Throttle Failsafe

Hi everyone.

Iv'e been flying with APM2.6 for a couple of months now and loving it.

Ive flown a lot of Auto Missions and have discovered what i think is a bug.

I have Throttle Failsafe setup so if i lose contact when in Auto, Auto should continue.

This has been proven that if i switch my radio off during Auto, Auto stays on.

This is deliberate given my location.

After a few flights when i know i am losing radio contact the Quad simply won't make the next waypoint. 

GPS is good, Compass is good. In fact everything is good but i just don't make it sometimes and i think i have found it after pouring over the logs.

2013-10-13%2019-04%2015.log

When i graph the ThrIn and ThrOut i can see the ThrIn drops to 0 on a loss of Trasmitter which i guess is normal. But i see the ThrOut drop to 100 as well at the same time. 

Now i know that continuing Auto with a loss of Radio is probably a little unusual for most users but it's a feature i rely on.

Attached is the log as well as screenshot of ThrIn vs ThrOut.

Im hoping Randy or one of the developers can sort this out or maybe in the new release it already is.

Anyway cheers :)Untitled.jpg

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

Join diydrones

Email me when people reply –

Replies

  • Hello Motion Man

    Have you tried going to Radio setup in Mission planner where you can see the radio inputs? Place sticks/mode in "flying position". Then turn off the transmitter and see on the bars if all channels are going to failsafe at the same time and to the expected values. Also from TLog you can graph the input channels.

    On my setup I discovered putting throttle failsafe from 975ms to 900ms made the throttel channel go to failsafe delayed compared to other channels. On Turnigy 9x/OpenTX/Frsky  See graph from my TLog.

    3692856016?profile=original

     

     

     

     

     

     

  • Hi Randy, log attached from previous flight with Failsafe issue.

    thanks

    2013-10-13 19-04 15.log

    https://storage.ning.com/topology/rest/1.0/file/get/3691069265?profile=original
  • Developer

    I discussed this issue with Motion Man on github and I think it's all cool.  I believe the issue is that the receiver is changing the flight mode channel as it enters the failsafe.  AC-3.1 will ignore these changes but AC3.0.1 may not. 

    I think Motion Man may send me a tlog which would allow us to confirm.

    I'm pretty sure these issues will go away with AC3.1.   This check-in is also related to the outcome of that discussion.

  • Gee, "Drones-discuss" is like a fortress. Tried to Join and post but no luck.

    Hmm what to do next. A noob at online code sharing but an experienced coder :)

    Happy to help where i can. 

This reply was deleted.

Activity