2 flap individual trim

Hello

Sorry to make a possible dumb question but im programming a new model with 2 flap servos, i set flat to a 3 pos switch... everything works but im not able to use subtrim of each servo flap.

I mean i go to servo setup >> flap servo (1 and 2) >> subtrim do not make effect....

How can i subtrim each flap servo? and control the amount of flap deflection in each position of the switch?

Thanks and happy new year!

Hi

I assume that you have assigned the switch directly in the function assignment menue..
If yes, delete the switch from the flap control

The best way is to use the 3 pos switch for switching between separate flight modes.
in this flightmodes you can use the "flight mode trim" to set your flaps.

The reason why subtrim does not work is not clear to me.
Can you upload the file of your model?

best
Philip

Thanks for reply

Yes i have a switch assigned to flap in "Functions Assignment" menu, i understand why you mean. Yes i can upload the model but i don't have the radio with me right now. Reading i think i can use the butterfly function to do that also but flight modes is also an option.

Is extrange that subtrim do not work.... i can reduce the travel, reverse... but no subtrim.

I just updated my radio to 4.28 firmware version, but at Jeti told me that this have no "principal changes in the transmiter" so i asume this is not related

The newest firmware is 5.06 .. i am using 5.03 without any troubles.

Try to upgrade to 5.03.
Then create a new, fresh model and test it again.

I know is not the last one, but that version was recommended to me by jeti, history is that i bought a software function update and when sent me i can not install as i was on low version. Radio was working perfectly so i asked about the concern that i did not want changes in the radio as everything was ok and they literal said:

If you don't want any principal changes in the transmitter, I recommend updating to version 4.28 via JETI Studio

That's why i updated to use the feature i bought

Edit: i dont think is a version software bug... as version was recommended

Than stay with 4.28 .It works fine.

But try to create a new fresh model from scratch ...
Sometimes that helps to get rid of strange behaviour ...