Failsafe; Multiwii 2.2; Turnigy 9x V2; 8CH receiver V2; work

[E_TE_T]

Multiwii 2.2 + Turnigy 9x (original firmeware) V2 + 8Ch receiver V2
failsave worked.

I set in the controller Setting->Fail Saf -> All Channel are now F/S 000%.
(I can not say for sure whether it is necessary)

Then I started the motors and turned off the remote control.

In my case, after one second the motors were still running for 5 seconds (low speed).
Then all motors stop running.

here my code: (config.h)

#define FAILSAFE
#define FAILSAFE_DELAY 10
#define FAILSAFE_OFF_DELAY 50
#define FAILSAFE_THROTTLE (MINTHROTTLE + 200) (The value must be adjusted depending on the model, to achieve a descent)

E_T

[ardufriki]

Hi, what kind of receiver do you have? I am impressed, because AFAIK in Turnigy 9x and 9x8c receiver from HobbyKing there is no FAILSAFE.

In my case I have soldered a wire form the led inside, to get an analogic signal than I use later to trigger multiwii failsafe code (it is not a wonderfull RSSI signal but if I switch off my radio it works).

[yoan1509]

there is a rssi pin in the 8ch recever from turnigy
see
http://www.rcgroups.com/forums/showthre ... 19&page=15

[ardufriki]

oh, thanks, I will check that in my 9x8c v2. For now I have it connected just to the LED. I will give it a try.

[E_TE_T]

I have the Turinigy 9x V2 (original firmware) and the turnigy 8ch receiver v2.
http://www.hobbyking.com/hobbyking/stor ... ware_.html
No hardware were changed.



E_T

[ardufriki]

I have the Turinigy 9x V2 (original firmware) and the turnigy 8ch receiver v2.
http://www.hobbyking.com/hobbyking/stor ... ware_.html
No hardware were changed.



E_T

I cant make it work like you. I have the same tx rx combo

[E_TE_T]

I have this board:

http://www.ebay.de/itm/MWC-MultiWii-SE- ... 1142193717

The first 5 channels from the receiver are connected to the board.

In the Multiwii-software i changed this:

Config.h

#define QUADX
#define FAILSAFE
#define FAILSAFE_OFF_DELAY 50
#define HK_MultiWii_SE_V2

GPS (Not connected)

#define I2C_GPS

#define MAG_DECLINIATION 1.18f


Multiwii.ino

(Because my controller generates cannel-values ​​in the range from 1055 to 1886)

// ******************
// rc functions
// ******************
#define MINCHECK 1100
#define MAXCHECK 1800


E_T

[ardufriki]

Hi again,

I have tried that but it doesnt work. With MW 2.2 the motors continue running with last commands from sticks. May be there are versions of the rx ?¿?¿?

[E_TE_T]

In the video you can see that the receiver stores the last values, when signal is lost. After one second the failsafe-funktion are activated.

Here is the video that show it: http://www.youtube.com/watch?v=C9DrIlzB ... e=youtu.be

I can not explain now why the faisafe function starts?

E_T

[scrat]

Interesting...

[ardufriki]

In the video you can see that the receiver stores the last values, when signal is lost. After one second the failsafe-funktion are activated.

Here is the video that show it: http://www.youtube.com/watch?v=C9DrIlzB ... e=youtu.be

I can not explain now why the faisafe function starts?

E_T

Thanks for the video E_TE_T, it is incredible. I am going to investigate deeply why mine doesnt work like yours. Do you have PPM SUM enabled or something?

[felixrising]

I've got some problem with failsafe detection. I've got a spektrum dx7s + ar6115e which I've bound to remember a pre-defined failsafe settings which are center for everything except for throttle which goes to 990.. any reason this won't let it go to failsafe? It just hits minthrottle and the quad pretends to be a brick with minthrottle.

[Crashpilot1000]

Hi, Felix!
The failsave will engage, if the RX fails to send it's normal pulses. This also occurs if a RX -mwii wire gets disconnected. The RX MINCHECK is irrelevant for this function on multiwii (i think arducopter has some kind of this throttle - approach in its code). So setting a fs in your transmitter with throttle below mincheck (1100) will just put your motors to idlespeed (minthrottle).
Cheers Kraut Rob

[felixrising]

Okay, replying to my own post, I found this post http://www.multi-rotor.co.uk/index.php?topic=1014.0 by bunnygirl80 which mentioned the failsafe detect treshold [sic] value in RX.ino... "#define FAILSAFE_DETECT_TRESHOLD 985" which indicates that throttle needs to at least drop below 985... okay, I'll try to rebind and set throttle below 985...

[felixrising]

Hi, Felix!
The failsave will engage, if the RX fails to send it's normal pulses. This also occurs if a RX -mwii wire gets disconnected. The RX MINCHECK is irrelevant for this function on multiwii (i think arducopter has some kind of this throttle - approach in its code). So setting a fs in your transmitter with throttle below mincheck (1100) will just put your motors to idlespeed (minthrottle).
Cheers Kraut Rob

Define "normal pulses"... in that case, is there some way to get the AR6115e to not send "normal pulses"? Because it definitely won't enter failsafe at present.. also this page seems to indicate that it should work as well: http://www.multiwii.com/wiki/index.php? ... s#Failsafe but it doesn't for me.

[Crashpilot1000]

Hi felix!
In normal operation a rx transmitts pwm signals all the time to the flightcontrol, even with sticks in their minimal positions. If no pwm signal is detected in a certain timeframe an errorcounter is increased (something like a "missing heartbeat"). If the errorcounter exceeds a certain limit the mwii failsave is engaged. Different radios/brands do different stuff. Frsky for example. If you freshly bind an Frsky RX it will stop "heartbeating" on signal loss and the mwii failsave will engage. If you program a failsave setting into the frsky RX it will never stop heartbeating (sends failsavesettings on signal loss) unless it is physically destroyed / cable disconnected etc. So on the not so cheap radios (like yours) the failsave is a two stage process. The first stage of failsave is the correct failsave setting of your RX to send appropriate data to the mwii (center some sticks, some throttle, flightmodeswitch etc). If the RX fails (disconnect, electronic failure etc) the heartbeats will stop and the mwii failsave will come into play as the second stage of failsave.

EDIT: Sorry for OT spam!
Back to the topic. E_TE_T i think the turnigy rx must send some grainy pwm signals to the mwii on signal loss. So the readout has some timeouts and increases the errorcounter to engage failsave. The gui is probably too slow or too filtered to show that.

Cheers
Kraut Rob

[E_TE_T]

Back to the topic. E_TE_T i think the turnigy rx must send some grainy pwm signals to the mwii on signal loss. So the readout has some timeouts and increases the errorcounter to engage failsave. The gui is probably too slow or too filtered to show that.

Cheers
Kraut Rob

Once I have time, I look at the signals with an oscilloscope.

E_T

[E_TE_T]

Ok I testet the signals with an oscilloscope.

The receiver stops any signal after signal loss.
This explain why it works.
Now I just have to figure out why it did not go with 2.1 multiwii.

E_T

[rickmorel]

by felixrising » Thu Mar 28, 2013 8:21 am

Okay, replying to my own post, I found this post http://www.multi-rotor.co.uk/index.php?topic=1014.0 by bunnygirl80 which mentioned the failsafe detect treshold [sic] value in RX.ino... "#define FAILSAFE_DETECT_TRESHOLD 985" which indicates that throttle needs to at least drop below 985... okay, I'll try to rebind and set throttle below 985...

My problem with the 9x was I seemed to have a very narrow range where I could arm/disarm and Failsafe came on. Sometimes after disarming, it would Failsafe and I had to increase the throttle a bit to get back to normal and be able to arm. Seems I was constantly having to change the throttle trim. Turning off the transmitter always resulted in Failsafe.

Here's how I solved it. In the "RX" module, change:

#define FAILSAFE_DETECT_TRESHOLD 985
to:
#define FAILSAFE_DETECT_TRESHOLD 900

Now I can set throttle trim where I want it and it won't Failsafe unless I turn off the transmitter.