I am writing this after I experienced the same situation for the second time.

After my forum post yesterday (here), I thought Arducopter 3.0.1 release sounds good. BUT, I made sure it was not my manual mistake, made sure all connections and possibly everything on my end is fair and lovely. I even changed a couple of motors which seemed to be a bit skewed due to earlier crash.

It was then all was ready to fly again, happy and forgiving.

3691042400?profile=original

I was in stabilize mode (all my 6 flight modes today were stabilize), happily steering with my transmitter, better tuned, better flight but OFF IT WENT AGAIN  (if I remember correctly from a height of 10 meters) - Flipped and THUP THUP directly on to the ground - No fore-warning!

Once on ground, I picked it up and tried to see if it was my fault, doesn't look so, all props rotate like a charm synchronously!! When I connected via USB, all logs disappeared (like erased automatically, I am unable to enable them now) :(

What is happening? Is that a serious bug with firmware 3.0.1? If so, please let me know so that I can switch to an earlier revision. This is happening the 2nd time for a similar situation.

3691042476?profile=original

It might be a good idea to have a look at the log for my previous crash here so that others may not face it. It can be really dangerous :( :( I ain't blaming anyone, but it is fair to introspect the copter!

My copter survived due to my great innovation of foam pads as landing gears and lunch box protection plus my 3DR quadcopter fell on mud. Saved my electronics, motors may sound cheap to get, but if I break one everyday I become literally bankrupt!!

Regards..

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

Join diydrones

Email me when people reply –

Replies

  • As mentioned above, you hit throttle failsafe twice in the flight. Don't be so quick to try and induce panic about a 'serious bug'.

     

    "5: Throttle failsafe: ECode 1: throttle dropped below FS_THR_VALUE meaning likely loss of contact between RX/TX"

  • Without logs, its hard to tell. Your previous log was a bit of a mess which is why I didn't answer - but as a minimum it looks like you have some radio problems you need to sort out first.

This reply was deleted.

Activity