I think the issue is the application doesn't keep note of the slider position correctly.
New servo position = old position + slider movement value. If value is > max servo travel, then that servo is limited to max servo value.
Pitch adjustment in spirit-settings windows software
Hello,
the problem was replicated when doing very fast movements with the sliders on a slower computers.
We will fix it in the upcoming version 3.2.3 or 3.3.0.
Thank you for the report!
the problem was replicated when doing very fast movements with the sliders on a slower computers.
We will fix it in the upcoming version 3.2.3 or 3.3.0.
Thank you for the report!
Spirit System developer
Thanks for fixing this bug in 3.2.2 (released today).
The swash can still be adjusted so that it ends up un-level if one slider reaches its endpoint.
When this happens, all sliders should stop moving to prevent an unlevel swash.
To reproduce, set PIT servo to -100, and all others to 0 (pretend that is a level swash).
Enable "pitch adjustment" and move AIL slider to -50, then back to zero.
Remember: the swash will be level if the PIT slider is -100 and the others are zero.
This is not the case - the level swash has been lost and will need to be re-levelled using a swash leveller.
The swash can still be adjusted so that it ends up un-level if one slider reaches its endpoint.
When this happens, all sliders should stop moving to prevent an unlevel swash.
To reproduce, set PIT servo to -100, and all others to 0 (pretend that is a level swash).
Enable "pitch adjustment" and move AIL slider to -50, then back to zero.
Remember: the swash will be level if the PIT slider is -100 and the others are zero.
This is not the case - the level swash has been lost and will need to be re-levelled using a swash leveller.
jjuk wrote:Thanks. If any servo reaches the limit, I think all servos should stop. This will prevent the swash from being un-level.
There was no change yet in the currently released version. We have to focus and debug the issue on a slower computers. Quick fix could make much more troubles so it will be likely fixed as I said previously.
Spirit System developer
Internesting. I can't reproduce it on the "demo" mode, so maybe its something to do with writing the new value to the spirit in real-time?
I have a fast-ish PC, Core i7-6700 3.40GHz that shows the issue when connected to a spirit, and also a really old slow core-i3 that I can test with, if you want me to help.
I have a fast-ish PC, Core i7-6700 3.40GHz that shows the issue when connected to a spirit, and also a really old slow core-i3 that I can test with, if you want me to help.
Yes, it is related to speed of writing. In some cases the GUI thread is processed improperly/in a wrong order than communication thread.
In Demo mode and also with Wifi-Link connection there is no delay.
In Demo mode and also with Wifi-Link connection there is no delay.
Spirit System developer