You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the Turnigy Evolution is delivered in several combinations of Stick-Modes where the gimbals are just swapped and rotated. I don't know, how this is done with the fs-i6s.
There are two ways to get every combination solved:
preconfigured Input-Mappings with a Menu für the User
dynamic mapping while calibrating the sticks (like in most of the FPV-simulators out there)
For the second option i tought about a step-driven calibration routine:
All Sticks to middle, wait for User interaction (klick go!)
"Please move throttle-stick to full throttle" (wait for ADC change with timeout)
(getting which stick is moved, the max endpoint and if we need to invert)
Please move throttle-stick to zero throttle" (getting the min-value)
repeat for the other sticks
any pro's or contra's?
Im trying to implement it in my own fork (for learning C, of course :) )
The text was updated successfully, but these errors were encountered:
I think they are swapped. Mine came in Mode-1 already, so the mapping in the original branch was false.
It seems that there are no pins for the neutralization spring on the throttle gimbal. https://www.youtube.com/watch?v=o9QNUzk90YY
So they are swapped and rotated by 180° to let the cables come out in the middle... If you ask the user every step, it takes longer, yes, but you only do this once...
It seems that the Turnigy Evolution is delivered in several combinations of Stick-Modes where the gimbals are just swapped and rotated. I don't know, how this is done with the fs-i6s.
There are two ways to get every combination solved:
For the second option i tought about a step-driven calibration routine:
(getting which stick is moved, the max endpoint and if we need to invert)
any pro's or contra's?
Im trying to implement it in my own fork (for learning C, of course :) )
The text was updated successfully, but these errors were encountered: