Ok,

With Test 17, if I turn the Tx off without it plugged in it will do the fast twitching until the link is regained.

With the original 1.0.25 firmware (and some of the other tests that we ran) if I turn off the Tx when it is not connected to the computer the heli does nothing and just wait's for link again.

Thanks

Here is next testing FW:
http://spirit-system.com/dl/fw/test/spi ... test18.bin

If it does not help, I've added simple check if the software is running.
http://spirit-system.com/dl/fw/test/spi ... test19.bin

If so, failsafe is not activated.
I am very interested for results

_________________
Spirit System developer

Both do not work.

18 and 19 go crazy when the rx signal is lost and work again when the link is restored.

I also noticed Test 5 (I think) does the same issue on my G570. I put test 5 on there and when to fly today and lost link when the Tx was to close to the Rx and the servos went crazy as well.

Hmm, thats very strange. It is very interesting that it does not work, since nothing changed between 1.0.24 and 25 in this area.

_________________
Spirit System developer

1.0.25 does not have this issue with the original version.

It is only our tests. At least so far. I can test the original firmware (1.0.25) a few more times.

What did you change from 1.0.25 to now with the tests?

There is only fixed failsafe.
Here is FW without failsafe so it should be as with 1.0.25.
http://spirit-system.com/dl/fw/test/spi ... test20.bin

_________________
Spirit System developer

Here's some more info...

If I turn the heli on with the Tx off, let the unit initilize, then turn the Tx on I get normal link... However, when I turn the Tx off if I did it in this manor the heli acts as it should and does not go crazy.

When I Have the Tx on and plug the heli in with Test 19, sometimes only the rudder servo will work. all other servos do nothing. But if I reset it sometimes all works.

Also, if I hvae the Tx on when the FBL Initializes then turn the Tx off after initialization it will go crazy until link is regained.

Ah, so if I understand correctly, there is third kind of issue
I wonder if some of these issues can't be problem in TX or RX.
Nobody from testers are able to reproduce it with Futaba

_________________
Spirit System developer

Alright!

So far the best yet!

With the heli not connected to the PC when the rx looses signal there is no issue anymore with test 20.

Saving changes and opening the log causes no issue.

When the rx looses signal with it connected to the PC it is hit or miss. I tried about 15 times turning power on and off to the Tx with the heli connected to the PC and it went crazy only 2 of those times. Both times was right after I checked the logs.

However, When i checked the logs then turned the Tx off after it did not Always go crazy so that may have just been a coincidence.

I can't seem to find a routine that gets it to go crazy every time now.

Def good progress though! Best so far!

Good.
It still seems as a problem with data stream synchronization.
I believe it can be fixed totally even with failsafe

_________________
Spirit System developer