Some reason why I can't bind Hubsan since update?

Hey guys,
Just wondering why I can't bind my Hubsan X4 or my V949 with my Devo 8s since I updated to the newest version. I haven't tried a zillion different things (mainly because I don't know what I would try) but I just need to know if I'm missing something simple.
Thank you!

Sorry PB, I've been too busy to check answers to my own questions! So I think the last version was 2.1.1 (the one you put on) And no - I didn't copy the tx.ini over. Do you think that would do the trick? I'm not always on top of these things that may seem obvious to you guys.

Thanks for the help!

I actually just reread your post PB - and realized that I have absolutely no idea what you're saying with that update code. I really don't know how to go about doing that - but it would be awesome if I could get my things working again.

Thanks!!!!

Read this:

deviationtx.com/forum/6-general-discussi...ou-need-to-read-this


Basically you need to edit the Tx.ini file that comes with the 3.0 release and uncomment the lines corresponding to the rf modules you have installed in your radio. In your case the flysky module, so as PB was saying edit the file and uncomment lines:

enable-a7105 = A13
has_pa-a7105 = 1

to tell Deviation you have that module installed and it's available for use and all should be well again.

Hope this helps...

Thank you! I'll try that as soon as I'm done with my boring "work" work!

I really appreciate the response!

IT WORKED!!!! THANK YOU!

After I figured out what "uncommenting" meant - I was all set!

Thanks again guys... I'm happily buzzing around the living room again.