ZeXx86 wrote:I am sure we will solve the problem very soon together with JETI. You can use UDI, PPM or PWM in the meantime.
Thanks, ZeXx86. Looking forward to it.
Btw- Just had my first flight with the Spirit today. Nothing flash flight wise but the Spirit felt good and solid right from the outset. The integration with the Jeti was great for tuning too. Acro bailout brutal and precise....just what you want.
Hi Tomas, just loaded 1.2.1 into the Spirit and Exbus Failsafe still appears not to work. This is checking by turning off the Tx simulating a loss of signal. I have not tried pulling the Rx from the Spirit check yet. Is there anything else that needs to be set to get this to work besides the settings in the Rx?
You don't. It's like vbar, only Throttle goes to Cutoff. (I am assuming for now) Just testing it now. Will let you know how it goes. I have asked Tomas to put some notes in the changelog to make it clearer.
Last edited by buttles on Mon 20. Jul 2015 12:00:08, edited 1 time in total.
ZeXx86 wrote:Failsafe is working for throttle, aileron, elevator and rudder channels. So you do not need to configure anything.
The failsafe with Throttle works fine now if you turn off the Tx or pull the connection from the Rx to the Spirit. Thanks Tomas. Only bit I don't get is your reference to the flying controls. If I hold over full rudder during the test it just stays where it was. ('Hold' in failsafe terms) Is that all it's supposed to do? Thanks
If you are holding aileron, elevator or rudder stick all the time (even during initialization), then this position is calibrated as center position.
So if failsafe will be activated, then it will return to this center position.
Starting the unit with stick deflection is wrong as center positions are calibrated each time. If you want to check failsafe with these channels you should initialize the unit in the normal way.