Failsafe will not work, need help

[Mikelib765]

I have a micro f3 fc, flysky is6, and flysky ia6 receiver. Setup as pwm. Everything wired properly and bound. I setup up failsafe in clean flight to 885/2115 and channels 1-4 to auto and 5-6 to hold. Save and reboot. Reconnect to cleanflight. Turn off tx for failsafe test with receiver tab up, throttle pulse drops from 1000 to 885(same setting as failsafe). Everytime I change min failsafe pulse that is what the lowest throttle pulse is when tx signal is lost. Went into cli and tried to set rs_min_usec and rs_max_usec and reset failsafe settings, the throttle pulses go back to failsafe pulses so failsafe never works. Someone tell me a answer please. Tx failsafe also doesn't work, thank you.

 

[mozquito1]

Flash to an old firmware then back again or reset the board & try again.
There should be no need to go into cli.
Tx failsafe if you turn it off does the quad fall.

 

[Mikelib765]

Flash to an old firmware then back again or reset the board & try again.
There should be no need to go into cli.
Tx failsafe if you turn it off does the quad fall.

The fc had cleanflight 1.12 and I upgraded to cleanflight 2.01. The motors shut off when tx failsafe engaged but when I set throttle -50%, motor don't spin on failsafe, they just shut off.

 

[mozquito1]

I'm using virtually the same setup. 1-4 is AETR aux1 or channel5 is arm.
Aux2 or Channel 6 is modes. If you not arming by sticks. Is the failsafe tab in CF setup right. Have you set it to drop or fall slowly. I have nvr had failsafe on a switch other than the arm. If my Tx goes off, it falls. I have tested range failsafe & it worked. I wouldn't use a dedicated failsafe switch the arm button is good enough.

 

[Jackson]

I have nvr had failsafe on a switch other than the arm. If my Tx goes off, it falls.

Have you tried that approach with the i6's failsafe options?

 

[Mikelib765]

I'm using virtually the same setup. 1-4 is AETR aux1 or channel5 is arm.
Aux2 or Channel 6 is modes. If you not arming by sticks. Is the failsafe tab in CF setup right. Have you set it to drop or fall slowly. I have nvr had failsafe on a switch other than the arm. If my Tx goes off, it falls. I have tested range failsafe & it worked. I wouldn't use a dedicated failsafe switch the arm button is good enough.

Yes I had the failsafe set right in cleanflight but when the tx turns off, the throttle pulse drops same as failsafe setting and so failsafe doesn't engage. I guess I'll just use to flysky is6 failsafe instead just to kill motors when the signal is lost. But I just don't understand why when my tx turns off it doesn't drop to a certain pulse rather than dropping all the way down to the lowest pulse it possibly can

 

[Mikelib765]

Have you tried that approach with the i6's failsafe options?

Yes but it only kills motors and will not throttle if I was to set throttle settings for failsafe on flysky i6

 

[mozquito1]

Is the range set properly in the modes tab
Is it within the range you set.
I have never done failsafe that way.
The i6 is a good Tx with good range.
I have only ever had one drop out in one of the the biggest area I fly. About 600-700 foot. The boundary is 70' trees I climbed em once b4, never again so I stay clear.
The disarm or Tx i6 power button is all that's needed. Set it to cut props & drop.
Believe me it's safer. If it was falling on you would you want the props spinning.
I don't, not again lol.
Just looking back at what you said about it dropping down to 885. I've noticed that but all is OK. What are your switches.
I think it's something to do with the range in the modes tab for that switch.
I'm in work at the moment so going off my noggin. It's all so much easier @ my desk, now I just do it but it's hard putting it into words explaining something to someone who has no clue what I'm going on about yet. My setups are about 10 months old but good flyers. I know the inside & outs. But the other day I upgraded the SPF3 firmware,but in the past end points have been OK as in the stock settings. Flashed the esc's & calibrated the esc. I got to my area after a 30min walk only to find they ain't playing
Ball. So after 20min I noticed the end points had changed & seemed to have been altered on the reboot of the latest spf3 firmware. I have been flying with the quads recently. They were just hung up on the door after use & on Sunday I cleaned em & loaded the firmware.
So I never altered anything just did a esc calibration & the end points where correct on them. Through the blheli config tool, not blheli suite. I do have it but config tool is easier.