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:

1. preconfigured Input-Mappings with a Menu für the User
2. 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 :) )

After flashing the firmware for the first time the storage was not initialized correctly.
Modelnames were not available and the display showed weird characters.

I could fix this after using storage_load_defaults(); storage_save(); but it should work from the beginning.

As per subject.. is it necessary to use the flysky module?

For many... the stock module will be perfect - what they would want is an opensource firmware.

Hi,

Have you had a look at whether it is possible to port this to the new Turnigy Evolution?

https://hobbyking.com/en_us/fpv-racer-radio-mode-2-white.html

https://www.youtube.com/watch?v=ZMHVIhZzSMI

Cheers,
Andrew

When I tried to backup the firmware, I found that the mcu is read protected. I have no way to back up and the original data is erased. Could you please share your original firmware?
Thanks a lot!

As found out in #1, both transmitters have a 8Mhz crystal. The SYSCLK define in the makefile assumes 12MHz. I need to investigate why this is working correctly with the 12.000000 value in the makefile. All timings are correct (9ms frame time for example). Maybe i messed up the sys clock initializing somehow so that it assumes 8mhz input. I will have to take a close look.

Idea is to use the Turnigy Evolution in Joystick mode with 2.4Ghz video, however, I found that it's still transmitting when in USB Joystick mode.

Is there a way to turn that off? Either with some menu option like the Taranis offers or maybe by patching/hacking your firmware? It would also be okay if it's 'permanent' i.e. would require flashing a stock firmware to re-activate RF output.

has serial support been added. it would be nice to create a programer for future updates ect.
also to restore original functions such as HID joystick support for simulators ect.

example of opened joystick implementation opentx/opentx@86f136c

I just started to port this to use the open libopencm3 instead of the st peripheral libraries.
see branch opencm3 (not working yet)

@fishpepper, I recompiled the latest master and tested binding and TXClone again.
Unfortunately I still have the same issue:

Bind mode: Put the RX into bind mode (2 solid LED's), as soon as I hit bind on the TX one RX led starts blinking as it should indicating that it receives the bind packets. However upon restart of both TX and RX, the RX simply blinks indicating no connection.

TX Clone: I tried that next. Put the Evolution in Clone TX mode, powered my taranis up and hit bind. The evolution started with the autocalibration etc and finished with "please switch off now".
After powering it back up the RX still could not connect (powering the taranis up makes it connect instantly to the taranis).

Any ideas on what I'm doing wrong? I assume that the TX module connections are fine given it can send and receive (at least looks like that from the tests above). Could there be a HW connection issue to the module which would not show up during bind but only in transmit operation?

Also you recommended to check the hoptable and place a while(1); after the debug print with the hop table for now. => can you point me at the right place for that? I checked the src but could not find the obvious place for the hoptable debug.

Thanks !