Spirit System

Jman841 wrote: However, it also activates rescue. Not sure if that is a good or a bad thing. Could be nice if I loose signal but it will also cut throttle so may cause more damage. I think I just have to adjust channel 5 to be a positive value when failsafes go on.

Great, I guess default values from Tarantis are just not very good for S-Bus protocol. Btw throttle channel should be cutted of in case of failsafe - that is default behavior of nearly all ESCs, receivers and transmitters. If not, your model can fly away.

Simply this issue was caused by incapability of S-Bus protocol - it is not prepared well for values like 0, 0, 0, 0, 0, 0, because protocol is not able to recognize its start and end of the frame.
For example, my Futaba does not allow even to set failsafe for all channels. I think that it is because protocol limitation.

Ok, awesome!

Glad all is working now. I have all servos set to center (0) and the Throttle (CH3) and Banks (CH7) set to -100 with the Gyro (CH5) set to 70 to keep it out of rescue.

It's working perfectly!

thank you Tomas! Finally solved the problems!

I would highly recommend when you release the 1.0.25.1 to add to the Manual that if using Taranis with Sbus failsafes must be set to custom and not to "No Pulse". If you want I can update the manual for you.

Perfect, I am very glad we know where the issue is exactly and how to fix it once for all

Thank you very, very much.

Ah, ok 1 more issue cropped up through some more testing...

I just put Test 23 on my Goblin 570 and when I am connected to the computer with the Spirit software on and the Tx on all is good.

When I open a log, I loose control of the tx. I still have link with the Rx and the unit does not go to failsafe values, however, my tx does not do anything until I cycle the power.

This issue is present on both my G570 and the X3.

OK, I will try to fix it in few seconds.

Try this please:
http://spirit-system.com/dl/fw/test/spi ... test24.bin

Test 24 fixed the issue with opening the Logs, however, it is present when saving changes.

When a change is saved the Tx does not do anything after the change until power is cycled. Same as before when opening the log (It could have been present when changing settings before as well. I did not test it before) so whatever you changed to fix the Log issue should fix the saving issue as well.

Ah, I think, that this behavior is rather random, because such routine is very same for log and save.
This situation happened probably in time, when recognized signal is not valid - previously in this time servos started to behave crazy.
I will try to add another fix so it can fix even problem with default failsafe values.

Just tested with test 23 as it is on my G570. Same issue with saving as well.

However, what was weird is when I made the first save, the Tx stopped working. When I changed a second thing and saved again, the Tx started working again.