Devo receiver failsafe doesn't engauged

I don't know it is a bug or something that is suppose to work this way...

I've got 3 types of Devo receivers, RX1002, RX701 and RX601, two Devo Txs 7e and D10
today I test out the failsafe function and found that it doesn't work for all my receivers and transmitters.

After messing around for quite sometime, I accidentally found that my usual way of starting up my radio system is wrong. My procedure was:

1. Turn on the receiver
2. Turn on the transmitter. (or the other way, it doesn't matter)
3. While the binding message is timing out (11 sec), I manually stop the binding process by pressing ENT.

It works fine, no problem... other than the failsafe doesn't engauged. I find out today that I must wait patiently for the 11 seconds to time out without pressing ENT in order for the failsafe to work..

Is it designed the way it is? Would it be very inconvenient?

FDR wrote: Which version?

devo10-b9dae8a38714

FDR wrote: It's a version from Suvsuv's fork, not the main deviation repo.

PB committed a fix implementing the devo failsafe on 2012-12-04.
Your version is younger, so it can contain that fix, but only Suvsuv could tell for sure...

i see, thx

first you have to Fix ID the Bind of the Receiver .
this will stop or cut out the 11 seconds for the radio to find the Receiver ,,, then go to failsafe and do L125 on the Throttle servo ...
this needs to be done on all your Models ...
I have all different RX's and about 30 odd Models and they all working fine .
I have a Devo12s and it works in anyway i turn it all on ,,, But the rule is to always turn on the Radio first ....

Hope this helps you
Glenn

paiste2002 wrote: first you have to Fix ID the Bind ,,, then go to failsafe and do L125 on the Trottle servo ... this needs to be done on all your Models ...
I have all different RX's and about 30 odd Models all working fine .
I have a Devo12s and it works in anyway i turn it all on ,,, But the rule is to always turn on the Radio first ....

Hope this helps you
Glenn

Welcome to almost 3 years ago!

Hi I am not an expert, but I want to give some experiances with my FAILSAFE.
After destroying my HM-V540D03 in my test room, doe to tranmitter power off,
I resumed that failsafe is a must on all my flying objects !!!
Case A:
Flight Controller Bavarian Demon AXON with Walkera RX-SBUS Receiver and Deviation12s-V5 transmitter.
In this combination the Tranmitter power off caused a max. value on all cannels. The Helikopter was Spinning up to ist max. Rotation Speed.
Solution : since I bind with a fixed ID the AXON recognices a failsafe Status !!??
The Helicopter stops Spinning after About 2sec.


CaseB:
Flight Controller Naza L M (converted to Naza m V2) with Walkera RX-1002 Receiver and Deviation12s-V5 (nightly builds of 7.Jan.2019) transmitter.
In a YouTube Video it was mentioned that the rx1002 saves the failsafe values of the Transmitter, so I tryed that.
Again as in case A) I got the failsafe working just with a fixed ID !!??
The Naza requires a certain value on the failsafe channel to recognice the failsave Status. so I had to set this value to the failsave of this channel in the mix menu.
Thats why I now that the Receiver saves this failsafe value from the Transmitter. So I know the rx1002 has a failsafe function.

It would be fine if anybody could add more useful Information About failsafe and an answer why I recogniced a difference by using a fixed ID.

The autobinding doesnt work in both cases (A,B ) ???