[Solved] Jeti REX7 and Failsafe - Cannot get it to activate

[Thorvald]

I've been searching on this topic here and on Helifreak but nothing conclusive on how to resolve this.

I was trying to set my failsafe today with REX7 and Spirit Pro but the servos always hold last command.

I have tried the following:

1. Disable Failsafe in REX7, setup failsafe in Spirit Pro and then save settings. Turn off transmitter, servos still holds last position.

2. Enable Failsafe in REX7, setup failsafe in Spirit Pro and then save settings. Turn off transmitter, servos still holds last position.

EDIT: I am using the Windows software to configure the failsafe.

My config:
Jeti DS16 (Tx set to 100hz)
Spirit.bin v2.01 (download from this site not from Esprit lol)
REX7 firmware 1.02
Spirit Pro 2.01
EXBUS single wire connection


Is failsafe currently broken with EXBUS or is there something I am missing?

[ZeXx86]

You have to disable failsafe in the transmitter, then restart the receiver/unit and everything should work.

You should see that the receiver signal is lost in the log, when you turn the transmitter off. If not, then the failsafe can't work and the problem is only in the REX settings.

[Thorvald]

Hi Tomas, I did disable failsafe in the Rex7 via the transmitter and yes I get three different "Receiver signal lost" messages in the log.

However the channels do not move to the positions I set them to in Spirit, they stay in their last position.

Also the log after the Receiver signal lost messages I powered up my Tx and then the log showed a bunch of "Good Health" messages... so it can see it coming and going.

I tried again tonight with the 2.0.2 firmware and same issue, no failsafe activating. I've attached a log showing this.

The method I am using to test is set failsafe to "mid sticks" on all channels, then reboot everything. Then set pitch to max on Tx and turn off the Tx. The Pitch does not move back to middle (which is the failsafe position).

---

There is a further issue with this, we cannot disable failsafe in the Tx/Rx if we are not using the gov, we need the Rx to set the throttle to idle on signal lost!

[Thorvald]

Ok just confirmed that with Failsafe enabled we still get the "Receiver Signal Lost" messages in the log, so it is possible to leave Failsafe enabled in the REX7 so that the throttle goes to low and still see the change in Spirit.

However again, the fail safe positions set in Spirit via the PC software are not activating.

---

Anything I can do to help diagnose this? Maybe a way to check the failsafe settings or something?

Thanks!

[Malc1]

I'm using a regular R3 EX rx with failsafe activated because I'm using the throttle plugged directly in to the receiver.
The throttle channel is left unassigned in the Spirit software.

So I have failsafe working OK with the throttle no problem, but I am unable to get any other servos to go to preset positions with the Spirit failsafe setup tab.

What can I do here?
Is this the same issue really?

[ZeXx86]

To make it work, please assign throttle channel in the unit.
Make sure that the throttle is not too low (under 0%) in the failsafe, else it will be treated as invalid.

In the next firmware release we will make it so that this issue can't happen.

[Malc1]

I am using an external nitro governor plugged directly into a channel on the Jeti receiver so throttle has been unassigned in the Spirit software as required.
If I assign it in the software it will not work directly .Correct?

[ZeXx86]

It is possible to assign throttle and use it from your receiver at the same time. So there will be no problem.

But to make it correct, I have prepared updated firmware.
Here you can download (again) the file: http://spirit-system.com/dl/fw/spirit-fw-2.0.2-ex.4df

[Thorvald]

Thanks Tomas, that did it! Just assigned the throttle channel in Spirit (even though I don't use it) and now the failsafe activates. So at least I feel safer flying it until a fix comes out.

Cheers!
Tim

[ZeXx86]

You are welcome, but the fix is already out. I have linked it in my previous message.