Help!

 

My HEX crashed from a FAILSAFE / DISARM event in mid flight!

I have been successfully flying Quads & Hex's with previous firmware versions of Arducopter using APM 2.5 boards until Saturday afternoon's unexpected crash. For a long time I have been using 2.8 and then successfully migrated to 2.9.1b, after having to tighten up more on eliminating vibrations.

All functions ran fine on my Hex under 2.8 and 2.9.1b.  It is an FPVPilot aluminum frame, using RCTimer 880kv motors/ 30a ESC's, minimosd, apm2.5, mavlink, and fpv cam/550watt 5.8 transmitter.  I use a turnight 9x with the Dragonlink for flight control.

On Friday, I upgraded the APM firmware (after factory reset, erase) to 3.0 rc5, after my friend Francis had good experiences with 3.0 rc5 with his tricopter.  The only issue he was having was the toilet bowl effect from which some recent posting, Randy was able to help him with the Compass MOTor configuration process.  In any case, I did some minimal testing on 3.0 rc5 after updating and all functions seemed fine... Stabalize, Alt Hold, Loiter, etc...  in some pretty windy conditions.

On Saturday, Francis and I went out to the field to test mission planner.  The only thing I changed from the day before was I turned on FAILSAFE for RSSI and Battery.  I tested this on the bench, as advised, by powering on/off the dragonlink and watched the mission planner radio values, etc.

At the field, I began by flying LOS at first as usual before flipping to FPV.  At this point I  flying our a little further (less than 1/2 mile max...   and a little higher  (no more than about 50 ft).

After a few minutes into the FPV portion of the flight, motors stopped and it dropped to the ground.

I've attached a number of screenshots and the log file.  As you may see from the attached logs, that after a long DISARM state, I ARMED, then flew all around for quite a bit and then at around the 868 time mark at about 30 feet up (we were on a top of a hill flying out over a valley producing negative Altitudes at points) it dropped like a rock!.

After locating the crashed HEX, the APM was still in a DISARM state.

After playing the logs at a slow rate, I saw that for some reason in flight, a FAILSAFE occurred with an immediate DISARM (as if my throttle was at 0).  The battery was still strong.  I looked at the graph for throttle af the time the FAILSAFE occurred, just to make sure that in my frantic, I didn't lower the throttle to 0, and as you would expect I acutually maxed it trying to recover in some way.

I've checked everthing on the HEX and it doesn't appear to be electrical.

Since the crash on last Saturday, and reading about others who have had disarms in mid flight, I decided to go back to 2.9.1b, test for a while with "NO FAILSAFE", and see if the problem occurs again.  So far, with only minor testing around the house (not at the field) it appears to be okay.

I am very afraid that this will happen again and hate to have to go through all the repairs again.  I also would like to migrate to 3.0 fater the final release.

Even though I have not seen anybody else posting this type of severe issue with 3.0, could you review my log and help me to determine where the real problem may reside.  I am a novice at reading the logs but eager to learn.

In the meantime, I'll try to do some more robost testing with 2.9.1b with no FAILSAFE, just to get a "good feeling" baseline again...  hopefully.

If I should have the same issue again, and if before I get your advice, I'll fall back to 2.8 (where I have flown with this same HEX successfuly quite a bit).

2013-06-08%2018-43-23.tlog

Basemode%20Graph.pdf

FailSafe_Disarm%20with%20Status.pdf

Flight%20Data%20Play%20Back%20of%20Crash%20Point.pdf

Hex%2030rc5%20Snagit%20PID%20Best%20Values.png

PID%20Values%20for%20HEX%20at%20crash.png

Thanks a lot,

Mike Governale

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

Join diydrones

Email me when people reply –

Replies

  • Developer

    Do you have a dataflash log by any chance?  dataflash logs show the failsafe and errors info better.

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…