Wl toys V939

Hello,

here is my setup for the V939.

to bind the V939 you have to do some hardeware modifications on the transmitter, described here:

devo to flysky

Expo & Dualrate on mix 0,1,2.

works good for me and I hope for you too!

I used your model file, the V939 binds with my devo 10, but I have no throttle.

Another thing, It's strange that it only binds with fixed id 1111, if I set it to "none", the quad won't bind :/

The V929 work well with this model file to, binds and flies like a dream.

Here is my model file for v939.

It works well for me. FMODE is mode switch (0: indoor, 1:outdoor, 2:roll). RUD DR is the TH.
I am using the latest suv build of DEVO10. I DO notice that the switch assignment may go wired across some firmware build so you may want to check it out. personally I NEVER fly my heli with a downloaded config file without first checking it myself.
yet the other thing is that my v939 do need to manually bind to tx every time battery is replaced.

the following is an issue I found about fix id binding:
www.deviationtx.com/forum/3-feedback-que...939-very-short-range

blackmoon wrote: I used your model file, the V939 binds with my devo 10, but I have no throttle.

Another thing, It's strange that it only binds with fixed id 1111, if I set it to "none", the quad won't bind :/

The V929 work well with this model file to, binds and flies like a dream.

You're right, checking the model file is paramount.

I didn't bother because it is a micro quad.

My build of devo10 is from 21/02 devo10-5b6a882e48b5.dfu, can't say is to old.

What is strange is that the v929 works well with the file.

I had to start from scratch with the 939.

And what a nuisance having to bind again with each battery

With my Flisky th9x+er9x I almost modified a spare module with a normally closed button so I could power cycle the module to rebind.

Having to switch on tx while holding bind button a the back and all that within tree seconds of powering on the V939...

Then deviation came along, and the process is easier.

Edit: I already use a 4 digit fixed Id so it should be ok.

/ the following is an issue I found about fix id binding:
www.deviationtx.com/forum/3-feedback-que...939-very-short-range .

Thx for this, I haven't flown it more than 5 m from me so didn't had this issue, I'll check it.

The "power cycle rebind" issue has been annoying me for a while, with v939 and BNF v911. So eventually I took the code and implemented the quick rebind feature, in which case you can simply flip a switch (I use GEAR on my devo10) to initiate the rebind process, even more handy if you assign the same switch to reset the counting down timer. This feature has been incorporated into suv's latest build in case you want to try it.

blackmoon wrote: You're right, checking the model file is paramount.

I didn't bother because it is a micro quad.

My build of devo10 is from 21/02 devo10-5b6a882e48b5.dfu, can't say is to old.

What is strange is that the v929 works well with the file.

I had to start from scratch with the 939.

And what a nuisance having to bind again with each battery

With my Flisky th9x+er9x I almost modified a spare module with a normally closed button so I could power cycle the module to rebind.

Having to switch on tx while holding bind button a the back and all that within tree seconds of powering on the V939...

Then deviation came along, and the process is easier.

Edit: I already use a 4 digit fixed Id so it should be ok.

/ the following is an issue I found about fix id binding:
www.deviationtx.com/forum/3-feedback-que...939-very-short-range .

Thx for this, I haven't flown it more than 5 m from me so didn't had this issue, I'll check it.