Crossfire Nano Receiver Not Binding Fix

[@kobie4238]

Dude thank you so much. I jacked up my crossfire again is this was the best video to fix it. Im never touching the receiver again😮‍💨😭

[@MatthewTaylor3]

These steps actually worked with my TBS Tango2 (with minor changes to the steps). Thanks for posting this video.

[@beezermedia]

This is actually the same issue I'm having. I'm going to give this a shot tonight. Thank you!

[@twistedsocal]

Hey man, just wanted to say thanks for the positive attitude and your active responses to people, not just me. I'm sold, I'll subscribe if for nothing else, you seem like good people. Need more like that. Have a good one

[@edrone_]

Thank you I appreciate your support and know that you can always use me as a tool if needed and I'm willing to learn also

[@russelmoody4613]

Great job. Your solution didn't 100% fix my issue, but it gave me some new ideas which did solve my issue. Liked. Subscribed.

[@TonyKorologos]

Do share what you did. Thanks.

[@JustinRayHadley]

Thank you Man! I Have Been using this video to help many TBS users get back up and running after update issues

[@georgitushev]

Dang nailed, short on point, thank you brother!!!

[@kristen7192]

yep go thru the steps it works even got a bricked one to reflash aug 2021

[@ktmjay9920]

Thanks. Could not figure out what was going on.. had no issue until update.. thanks again..

[@tragicmagic5025]

Thank you, brother, very thorough in explaining each scenario

[@elsterfpv4904]

Thank you. I also have this problem ... unfortunately, I still can not update my rx on Agent X .. just does not do anything. Have now again the 2.93 firmeware everywhere on it and can fly at least

[@elsterfpv4904]

maybe it is because my opentx is not up to date .. will update it and try again .. next week

[@brunogp8269]

@@elsterfpv4904 I have updated my taranis to opentx 2.2.4, I have the 2.93 on the xfire, when I update to the latest firmware and I can't update or bind the receivers. So it's not the radio... It's this new agentx and software

[@SaverioGarzi]

@@brunogp8269 confirm, i did the same.... and it was the 1st crossfire setup for me... Not funny at all ^^

[@brunogp8269]

@@SaverioGarzi I'm back to 2.93 firmware it works. Hope tbs fixes this... It was a lot easier before this update

[@SaverioGarzi]

@@brunogp8269 yes, same, but i would like to try the new LQ and RSSI on the telemetry, without using the aux port... And it requires at least the 2.94 XD

[@AKtoTok]

Thanks man!! Super informative, subscribed!

[@albert4575]

Thanks man. This helped. Really appreciate it.

[@edrone_]

No problem please like share and subscribe!!

[@javarlewis9330]

Man thank you so much bro you saved my life! gratitude bro you earned my sub!

[@just_bright]

I've spent 7hrs at the table trying to BIND this. This is the last vid I'm watching. Flashing green rapid is my issue to the Tango 2

[@edrone_]

You can try downloading earlier firmware version onto your tbs tango 2 and see if you can bind after doing that. Let me know if that works and then I can try and help you update your receiver and tango 2 back to newer firmware versions. Try the oldest firmware for the tango 2.

[@just_bright]

@@edrone_ I've honestly given up and put all the gear up for sale

[@jerryzito6840]

Nice video. What you are showing makes sense. But when I Go to agentx I have no green lights on the firmware boxes. My crossfire module is solid green.

[@edrone_]

Do you have the receiver powered up and the module connected to your pc?

[@jerryzito6840]

@@edrone_ Thank you for the response. Everything is working. But one thing. I have the motor stop when arming on. I give it full throttle and it stays that way. Throttle stick seems to have no effect on the motors. Whatcha think? Do I need a throttle curve?

[@edrone_]

@@jerryzito6840 I always leave motor stop off. When I arm I want to see the motors spinning its safer that way. As far as your throttle have you checked the channel mapping in the receiver tab and tried moving all the sticks to confirm they are mapped correctly?

[@jerryzito6840]

@@edrone_ Thanks. My throttle is channel 3. It's moving correctly along with the other channels. It's also channel 3 in betaflight. Still goes to full power with throttle stick up, but does not come down with throttle stick down. Thanks for taking so much time with me. This is my first FPV quad.

[@intillanes]

Thank you so much. 1 am and my drone just started to work. I owe you a beer!!!

[@edrone_]

Happy to help please subscribe!

[@gaddivo]

I don't know which version I was at. Lucky I was able to bind the nano receiver via TBS Agent-X's bind button. Maybe TBS has fixed this kind of problem.Cheers !

[@JohnConservative]

Please tell us about what you used to wrap the quad arms?

[@edrone_]

It is 1/4" wire loom like for speaker/ automotive wires

[@skullh2060]

Thank you so much this helped a lot

[@outboxfpv4360]

Nice one👍 but I have updated my and tx module now all my binding in all quads have gone. Its solid red and pain to reach the bind button on the rx. Is there anyother way to get the rx into bind mode without pressing bind button?

[@edrone_]

Unfortunately you need to press the button to be able to rebind to the receivers the only time you don't need to push the bind button is on new receivers when you first power them up they are in binding mode

[@peterpichler8986]

Excellent analysis - thank you! In my case, I installed a CRSF nano Rx from the bundle, that I originally purchased and expected the FW update to take place over the air automatically. But the Rx did not show up in the LUA script and would not bind... So I connected the Tx (micro module) to my PC via USB and started TBS Agent X. Binding immediately worked and the FW update followed flawlessly... Obviously, it would be a problem for the Tx module to store more than one FW update (for updating different Rx FW versions OTA) but TBS Agent X can download everyting from the Internet.

[@garretpickens5745]

You the man, thx a million.

[@edrone_]

Your welcome glad to help please like share and subscribe 😉

[@EbrFPV]

Not run into this problem yet, but sure nice to know.

[@Slash7FPV]

Well explained, thx man! Helped

[@SunriseWaterMedia]

You saved me! 👊

[@jamiearmitage2002]

PRINCE! thanks fella

[@WeMakeLaw]

A firmware downgrade worked for me. After that, the upgrade to the latest firmware and binding worked too. Thanks

[@xerovolume3321]

Just use the bind button from TBS Agent-X Configuration screen while your TX is plugged into the PC and the RX is powered up and in bind mode (green light flashing after pressing bind button). If the RX is powered up for over 1 minute then you can no longer enter binding mode by pressing the button.

[@edrone_]

Great information. This video is referring to if your receiver will not enter bind mode by pushing the bind button or using the app. Force bind recovery seems to fix these issues if all else fails. Thanks for your feedback.

[@fpv_lewy3813]

bro you really saved my life with this its crazy! you earned my sub fair and square and Im going to document this issue In my book of fav notes haha

[@edrone_]

Thanks kindly!

[@dorelcodrutpatrasca2993]

Great one to know, yesterday I update the tx and I had 2 problems, first like on yours the radio refused to bind and instead of those hold long click and wait and so on, I just plug the cord into the tbs tx and from app I clicked bind and all was good, second problem because of the wrap and conformal coating on one of the 3 quads the button(metal plate its it's not a actual button) didn't work so with some angle twizer I rip apart the metal plate and I shorted out the rx and I manage to put the rx in bind mode, hopefully it is helpful for someone

[@bongarcon8806]

6.10

[@VeryViciousVice]

Thank you so much for this. Been making me crazy

[@twostep7189]

hey i got the both flashing green after they are both on same version but they wont bind do you know why?

[@VeryViciousVice]

@@twostep7189 confirm the newest newest LUA ctrossfire script for ur opentx radio. This is a separate download then opentx or the tbs launcher thing. I had an old lua script on my radio.

[@twostep7189]

@@VeryViciousVice Thanks man, i have the micro module, i have tried almost everything but this, i have tried to update it with out lua script, and it just kept blinking green as if its in binding mode but they just wont bind.. thanks again man ill try this and get back.

[@twostep7189]

@@VeryViciousVice hey man, i have had the newest version of open tx 2.3.7 and it has a new tools tab now with crossfire lua built in i think, i have tried via that and nothing..

[@doktordrone]

hello Ed, my tbs tango2 wont bind with my crossfire nano rx and i dont know how to update my rx, could you help me, please?

[@edrone_]

Sorry to hear, did you update your firmware on your tango 2?

[@doktordrone]

@@edrone_ no, i didn't do anything on my radio

[@edrone_]

@@doktordrone OK because I know I had updated one of the firm wears on my Tango to to the newest and it would not bind I had to go back 1 version I'll drop the video links you can watch my video and see if that helps

[@edrone_]

@@doktordrone kzbin.info/www/bejne/pnK2e4iqnLamb6c

[@igaaryawrs2957]

👍

[@caringcenter5375]

hi, i try 06:50 but still fast blinking led. any solution?

[@edrone_]

If the receiver will not go into recovery mode you may want to contact tbs or the vendor that you purchased from you may need a replacement

[@doktordrone]

Thank you very much for this useful sharing 🙏🙏👍❤️☕️

[@twistedsocal]

I have never once had more than just the rx and tx show up on my agent x, guessing you have your quad fully powered on when you do this to get all those things to show up?

[@edrone_]

Yes the receiver must be powered up for the tx to see it and show it on the agent x

[@twistedsocal]

@itsalmostover use agent and rebind the tx, it should force the rx into bind mode and should be ready to rock right after that, worst case upgrade to beta or downgrade to an older version of the firmware in process and it's much more likely to find the rx. I just went through this yesterday, now to get my f7 fc to actually see the damn rx

[@Victor90NOR]

what if you buy a new receiver that has a unknown firmware? Do i have to add every firmware and check if it will bind? my nono diverity will not bind at all. so it will not show up in my agent x.

[@DogWsd]

I updated the TX first and after plugging in the qwad th RX led was red. All I had to do was hold the binding button on the rx until the led started flashing green, opened the lua script and was able to bind without any problems. After they were bound the rx was updated ota.

[@edrone_]

Sometimes the standard procedure does not work

[@taterfpv]

Hey man thanks for the tips. I had this exact same issue with a nano that was red after upgrading the Tx module first. Downgrading allowed me to be bound and fly this quad again. The problem now is that I cannot update any of my nano Rx's that were running 2.93! I had moved on to some other builds and had the flashed the Tx up to 3.23 and the newer builds worked fine. I pulled these 3 off the shelf and none of them would bind anymore. I pulled my hair out for a while over the first quad until I found your video. Now, when trying to upgrade the nano Rx's using TBS AgentX, with the TX attached to the PC, nothing happens. The Upgrade button goes grey and that's it. If the Tx is on any version but 2.93 the receivers are not seen at all by agentx and are red lit. When I plug in a 2.93 quad, the button on the Tx changes from Orange to Green to show it's bound but AgentX will not pass an upgrade to any of my 2.93 receivers. I can upgrade and downgrade the Tx all day long but the Rx's are only seen by AgentX if it's on 2.93. I've gone as far as installing AgentX on a PC where it has never been installed. No difference. Tried 2.02 and 2.25 versions of AgentX. No difference. It's 2 AM and I have been messin with this for hours. Reminds of the FrSky days except I pay double to be frustrated :) I have no idea what to try next. Maybe stamp collecting is more my speed. Thanks again for the help with my initial issue.

[@edrone_]

At this point i would reach out to TBS customer support seems like a software issue on their end. Good luck let me know if they are able to fix the issues.

[@taterfpv]

@@edrone_ Last night, when it flashed blue indicating the receiver needed to be updated, and I short pressed the button to initiate the update, it would just go orange again. After upgrading the radio to OpenTX 2.35 and updating the bootloader (I had an old one 2.2.1) I got the button method to push the update to the first receiver! This time it worked so maybe this will help someone else. Edit: I should add that after the update was pushed it was necessary to re-bind the receiver using the lua script. All 3 working now.

[@monacocross4241]

i have tango 2 ,tray procedure , update Crossfire , after when need bind come red light , press button but nothing , hold nothing a gen ...... looks like button broken no idea ;

[@SkullDrones]

greetings friend! that week I had a problem like this. I did the TX update and could not bind the RX in any way. I spent hours pressing the button here, button there until magically something happened and TX recognized the RX, creased and updated the RX firmware. so far I still don't know what I did and in what order ... Thanks for the great tips! a big hug from Brazil!

[@Siamect]

Soo we are back to the old press and power up which requires 3 hands, and the receiver update that used to be a really great way to do things, is just gone. And I just had another failsafe the other day 30 meters out... I don't really see why I should continue with crossfire.

[@edrone_]

Yes it is frustrating however it's not something you'll have to do all the time hopefully I've only had to do it once and as far as failsafing I've yet to get one

[@Siamect]

@@edrone_ Just have to correct my former statement... I made the upgrade today from v2.42 to v3.23. Could not upgrade the receivers through the Agent software so I upgraded the TX first. I was able to just do a bind from the TX and then power up the quads and they upgraded automatically and bound the normal way without using the button on the RX. So I guess I have to apologize to TBS and Trappy for assuming it wouldn't work that way. But the question is why did you have those problems and I didn't...?

[@edrone_]

@@Siamect one of my receivers bound right away the other did not i guess it was stuck in bound mode but not connected to my tx is my guess

[@MattPochwat]

Hey edrone, I've had a lot of questions for you but I'm slowly trying to make my way through this crossfire setup. I appreciate the advice! I've run into a problem where when I try to update my rx from 2.42 to 3.23, the update button in agent x doesn't do anything. Sometimes it lets me press it, but then the update doesn't happen. Any ideas?

[@edrone_]

What kind of pc are you using?

[@MattPochwat]

@@edrone_ Dell xps 15.

[@edrone_]

@@MattPochwat windows 64 or 32bit?

[@MattPochwat]

@@edrone_ 64

[@edrone_]

@@MattPochwat maybe try deleting the app and reinstalling try again

[@vektr6278]

I dont get it. How do you make the nano rx to show up in tbs agent x. So how could I update my rx 1st before updating tx. Its not shown in my agent x. Im using a Tango 2 radio btw, the xf fw is relatively new and not much old fw exist

[@edrone_]

You have to bind to the receiver, once bound power up the receiver and then connect to agent x app. You should see it recognize your receiver while its powered up and connected.

[@twistedsocal]

@@edrone_ u can't bind unless the rx is powered up first. But yeah gotta rebind

[@madladdan]

How do we do this now in 2021? When my rx is detected by pc it doesnt show option to update

[@ugurasan58]

Worked... Thanks

[@edrone_]

Glad to help please like and subscribe!

[@jgpg420]

I dont understand this at all cuz if my tx inst talking to my quad how are my receivers going to show up in the tbs agent so i can update them first? I updated my crossfire tx, and now both receivers power up solid red and i then put them into bind mode by pushing the button. However, when i press the bind button on the taranis, it just says binding for like 1 sec and then it disappears and doesn't bind.

[@edrone_]

First make sure your firmware is the same for both your tx and rx you can roll back firmware if needed also if the receiver is not communicating you can force it into recover mode which will make it bind

[@ModeratelyCrazy]

@edrone My CSFR Nano Rx won't bind and basically jumps straight to slow blinking red when both it and my Micro Tx V2 are in bind mode. Any ideas?

[@edrone_]

Try going back on the firmware on the radio and rebind

[@ModeratelyCrazy]

@@edrone_ Downgrading now. Will post an update when I'm done for the benefit of the chat.

[@ModeratelyCrazy]

@@edrone_ No Luck: Here's what I'm doing: 1. I put the Crossfire Nano Rx receiver into binding mode (slow blinking green) 2. I put the Crossfire Micro Tx V2 into bind mode (single click on the module itself - slow blinking green) 3. The Rx then starts blinking Red at a medium to slow interval. 1. After this I need to turn off the drone and reset the Rx by holding to bind button and powering up the drone again, which puts it back to fast blinking green, then have to press and hold the bind button again which makes the light double green blink several times before going back into bind mode again) I think the Rx needs to be updated, but I don't know how to do that, and I'm not getting any recognition of the Rx on the my RadioMaster TX16s with the Crossfire Module in terms of the pop up asking me if I want to update the Rx like I've seen in some posts. RadioMaster TX16s Firmware: 2.3.14-otx (1e09791a) Rx Firmware: ???? Tx Firmware: 6.07

[@edrone_]

@@ModeratelyCrazy what happens if you leave the receiver powered up and don't power cycle? You should see update receiver after the receiver is powered up and in binding mode with the transmitter also in binding mode

[@edrone_]

@@ModeratelyCrazy kzbin.info/www/bejne/e3PLqoOhecSbodE

[@michaeldyer6079]

So do I put the newer firmware on the TX "that originally would not bind to the RX" before I do that button work around?

[@edrone_]

Correct tx first then rx after you bind

[@michaeldyer6079]

@@edrone_ I'm trying to put crsf shot on, my tx fw goes on fine. Thank you for your video. I'm gonna try it. My rx's wont bind to save my life.

[@michaeldyer6079]

So I put the crsf shot fw on tx, then do the rx?

[@michaeldyer6079]

@@edrone_ when I do it like you said, holding the buttons in that order I do get the blinking green light. But when I go to bind it the RX just turns blinking red again

[@edrone_]

@@michaeldyer6079 Are the tx and rx same firmware versions?

[@Tedzo177]

Just an update with my experience in case it can help someone..... I just got a new Micro TX V2 for my Taranis Q7 and was having serious binding issues. It was faulting out during the rx firmware upgrade part of the process shutting it down in bootloader mode. I was massively confused as my TX came shipped with the most recent firmware on it. After two days of chasing my tail I decided to actually try DONWGRADING the firmware that came on my Micro TX to the previous version....voila. As soon as it did that my binding/updating process was smooth as silk. ...So...if you are going nuts with a new Crossfire Micro TX version 2... try downgrading the firmware in TBS Agent X. Hope that helps someone that was struggling with the new unit!

[@Vihefex]

Well good sir, only one thing to say : thank you so much ! My nano rx was bound but no input whatsoever was going to betaflight from my qx7. Your fix worked.

[@TheMightyBinturong]

+1000 for this tip mate! I received my crossfire micro tx v2 today and spent a frustrating couple of hours trying to bind it to my nano rx with no luck. But downgrading the firmware version from 3.73 to 3.72 did the trick. Also, I suggest binding the RX through the TBS agent with the TX connected to a computer USB port rather than having the TX mounted on the Taranis

[@gregorydahl]

The module should update the rx during binding process .

[@edrone_]

Yes that is the way it is supposed to work now but when I made this video the software was older so it required you to do a force recovery to bind sometimes.

[@pacificnorthwestpilots6050]

Nice! Subbed!

[@falkorfpv570]

Nice video! I have a different problem that I can't find an answer to and hoping you could help. I bought a new nano and after trying to bind to my receiver, at first it worked as normal when I put the TX in bind mode, it even updated the nano but after that the nano started flashing red and then green back and forth. Now it's stuck doing that, do you have any advice on what's happening. BTW I put this nano on an Eachine Wizard X220 if that matters at all. Appreciate any help!

[@edrone_]

Try and update the receiver on the computer to the same firmware as your tx, if it wont bind then do the force bind procedure

[@falkorfpv570]

@@edrone_ My RX won't show up on my computer, how do i update it? Should I update my TX to the newest and try binding again or just force bind?

[@edrone_]

@@falkorfpv570 try updating to the newest on tx then try and bind

[@falkorfpv570]

@@edrone_ Will do👍, seems like the next logical step.

[@falkorfpv570]

YES! It worked! Thanks for your help and patience!

[@firantey_]

My crossfire Rx has solid green and doesn't bind. I tired the technique pressing button for 10 sec and once both. Its still not in bind mode. Help

[@edrone_]

Have you tried pressing the button one time?

[@archer4922]

I’m on my journey to crossfire now. Did the mod and got everything done on the radio but having an issue connecting the micro tx to my computer. I open up agent x and plug in the tx but nothing happens it just stays on the screen saying plug in your device. My windows version is 64bit. I even tried the impulse driver fixer and zadig and nothing. So I donno what to do to update it. I think it should be on the latest version anyway my buddy said he was able to update it just fine. So it could be my computer. I’m gonna try a different computer in a few. Hopefully that will work.

[@edrone_]

Sounds like a driver issue maybe try downloading the betaflight drivers and see if your computer will read your tx

[@archer4922]

edrone cool I’ll try that if the other computer doesn’t work

[@archer4922]

edrone that could be part of the issue. I don’t even have betaflight in that laptop. Only have Flightone on this one. My other one has betaflight on it. Fingers crossed it works when I get back home.

[@archer4922]

edrone yep driver issue. Worked perfectly fine on my other computer. 👍.

[@dario_hxc]

Great vid, edrone! What if it is a new build?

[@dario_hxc]

I’m running fw 2.31, and the nano rx is brand new out of the box.

[@edrone_]

@@dario_hxc is the rx firmware written on the packaging? Or in the Description of where you purchased?

[@dario_hxc]

edrone sadly, no. There’s no info on the package label nor on the eBay purchase.

[@edrone_]

@@dario_hxc I would try and see if it will connect And if you can't get the receiver to connect to your TX try the steps in the video

[@dario_hxc]

edrone thanks! I’ll try it again. Cheers from Ecuador.

[@TheReanim8ted]

How can you have your quad bound to your transmitter when this is the exact issue you are trying to resolve??

[@edrone_]

You have to force the receiver to go into binding mode by pushing the button on the receiver as instructed

[@TheReanim8ted]

edrone yeah but the issue is it won’t bind.

[@edrone_]

@@TheReanim8ted even after a force bind procedure?

[@twistedsocal]

@@TheReanim8ted the button press procedure forces the rx to reboot into a bind mode and stay there for a certain amount of time. Basically it forces it to drop all previous bindings and makes it factory reset unless you cooked your rx or maybe conformal coated the damn thing which would disable the ability to click the tiny ass button, the procedure shown in this video will work. You just have to do it perfectly. Have someone help if you need an extra set of hands

[@doktordrone]

Brother, i need help: tbs crossfire nano I let go of the antenna when flying, after that the rx keeps flashing, after I bind the receiver is connected but disconnected again after the battery is removed. Is my RX broken? thank you

[@edrone_]

What is the led doing on your rx and tx when bound and after power cycle?

[@doktordrone]

@@edrone_ before it green blinking and solid green after i rebind, and green blinking again after battery is removed

[@edrone_]

@@doktordrone any recent firmware updates on your rx?

[@doktordrone]

edrone yes, i update the rx when i bound it

[@doktordrone]

@@edrone_ i just connect tbs tango II and rx to tbs agent and it said: rx no configuration seeting

[@cobra350hp1]

It won't bind how do I do that then

[@aljazcernigoj8675]

Thank you

[@linzadagangster]

My nano has a constant red light but still seems to connect to the module Is the red light bad

[@edrone_]

Makes me wonder if something happened to your green light?

[@linzadagangster]

@@edrone_ what could happen to do that

[@edrone_]

@@linzadagangster it's just a led could have burned out

[@linzadagangster]

@@edrone_ well it turns green when I turn on the control but when I first got it it came pre assembled I connected a battery with smoke stopper but it stayed red . I noticed that the antenna clicked in like it was never really connected properly but it still stays red . Do you think updating it will fix it

[@edrone_]

@@linzadagangster first I would make absolutely sure your antenna is connected securely then you can try to update firmware but be careful that you update the receiver first then the transmitter and then rebind

[@twostep7189]

hey i got the both flashing green after they are both on same version but they wont bind, do you know why?

[@twostep7189]

ive tried everything in this videos and others

[@edrone_]

@@twostep7189 you may have to go back to older firmware on your rx then tx rebind and try again

[@twostep7189]

@@edrone_ i cant update my rx first? it doesnt come up on the agent x because it was never bound with my tx

[@edrone_]

@@twostep7189 did you try a force bind on the rx by holding down on the bind button?

[@twostep7189]

@@edrone_ yes i have done the emergency bind thing, however after the update is done and the rx and tx are on different firmware's the light on the back of my micro tx is blow i spess once to begin the update, light on rx flashes fast for update, then once update is done tx goes orange and i repower the rx, now they are both on the same firmware, i just watched them communicate no? anyway they both start to blink green as if in binding mode but they just wont connect, one person said they had an old lua script on there radio and it worked, ima try that, but ive bin trying to flash the update and bind them without the radio because you can do that i thought, ive also tried my OLD lua script to no turn out, noted this isnt my first time binding this garbage. Thanks for all the help man!

[@andrewmunch1292]

How do you update rx if you can’t get it to bind to tx….. like tf

[@edrone_]

Are you using TBS Agent X or M?

[@jebrc]

i have a brand new one that won't bind any idea why?

[@edrone_]

Is the firmware same versions on tx and rx?

[@jebrc]

@@edrone_ I have no clue I bought the rx a month ago and my micro TX is on the newest fw I got 5 and this is the only one that don't work

[@edrone_]

@@jebrc what exactly is the rx doing? What color are lights and how are they solid or blinking?

[@jebrc]

@@edrone_ it goes right into bind mode flashes green light as all do but will not bind I think it's faulty I tried everything

[@edrone_]

@@jebrc if you have tried all the steps of this video and other methods and it still wont bind i would return it as faulty.

[@jamesonkruger6989]

YOU RULE!!!!

[@edrone_]

Thank you please like share and subscribe!

[@sprayhood1]

hey dont get my new evouge 5 tbs nano talk to tango 2 using Tango II XF for bind

[@onetwo9824]

but if it flashes blue and light blue on a rx?

[@onetwo9824]

tried to downgrade it, but the drone is silent.

[@edrone_]

What radio/module are you using for your tx?

[@onetwo9824]

@@edrone_ tx12

[@arunratanakprak2161]

How can I connect the RX to my pc

[@edrone_]

After you are bound then then you will be able to see your RX in the Tbs agent X app If you cannot bind try rolling back the firmware on your TX and then retry

[@arunratanakprak2161]

@@edrone_ Thanks, it binds after I downgrade the TX firmware.

[@jasenhenry]

didnt work with diversity nano and tango 2

[@edrone_]

Thanks for the feedback have you checked which firmware you have on the receiver and tx?

[@jasenhenry]

@@edrone_ how do you check rx firmware version if it does not bind? i ended unsoldering it, replacing with another rx that also didnt work, then finally replacing it again. in this sequence it finally went into bind+update mode. i think residual power from capacitor and smoke stopper prevented the rx from completely powering down

[@srqcrna]

To me this is a real pain in the ass, they might make good stuff but 90% of the customers aren’t going to put up with this. TBS will never get market share selling crap like this. Just make a product that freaking works!

[@edrone_]

Biggest problem is different firmware versions don't always mesh well. Once you find a tx firmware you like and you get your rxs on a firmware that works well its all downhill from there.

[@leole9449]

Nice

[@PianoManPaul]

I am so SICK of buying brand new, "ready to fly" FPV drones.... that I can never get flying. This is the story of what very well could be my last one. I couldn't get a 'proper' crossfire bind at all, using a Nano TX module (on a BetaFPV LiteRadio 3) - Agent "Web" PC software SHOWED the bind as successful, and it detected bound with the rx - but NO radio input in Betaflight, the FPV reference in BF was spinning when I turned radio on, but showed no input from sticks or buttons) BUT I had previously upgraded both TX and RX to latest BETA versions. So NOW, if this a fault in the beta release.... when I go to DOWNGRADE the RX back to the public release, I get a message saying "No FW update using OTA" ... so I had no CHOICE but to downgrade the TX first, HOPING it would find the RX and consequently downgrade that as well. But .... that would have been too easy, wouldn't it. We can't have THAT. So here I am, sitting with my TX back on the safe, public 18-month old version 6.19 of crossfire - UNABLE TO DETECT my RX, which is still on that 3-week old beta, v6.33. I wish I had gotten into this when I could have used Agent X, instead of this very restrictive "Agent Web" ... THEN, shortly after finding THIS VIDEO, I'd be outside FLYING this effing thing instead of CURSING at it here in this gloomy dungeon my girlfriend hates. I was told I'd be better off starting with Crossfire when I got into FPV, and AVOID the NIGHTMARES of that absolutely mind-destroying world known as ELRS. So I finally gave up on that, bought a TBS Nano TX module, and a Crossfire-loaded GEPRC Cinebot 30. I'm giving myself 2 hours of finding the right answer to this, and after that 2 hours if I haven't found a solution, this radio, module, drone, and all my other ELRS unbounded junk collecting dust I've purchased in the last year, is going into the fire, and I'll be done with this horrifyingly discouraging dream of FPV forever.

[@magicpilot2914]

TBS Agent X app wont read my recievers

[@edrone_]

What pc are you using with what software?

[@magicpilot2914]

@@edrone_ Mac Pro latest model. I just fixed the problem. I had to refresh update in the TX, it was updated but apparently not working properly. Once i did that it did the binding and reciever nano showed up

[@edrone_]

@@magicpilot2914 glad you got it working. Any further questions please feel free to reach out. Happy flying and crashing!!

[@MatLittlePPG]

You son of a bitch! It worked!

[@edrone_]

Please like share and subscribe!!

[@spitfeueranna]

Every time you upgrade the firmware, you basically fuck up your system. Don't ever upgrade your firmware. This is the worst system ever. Bind buttons on your nano you can't find, stupid colors you don't understand, flashing lights and garbage and no idea what it's doing. Now my system is fvcked up and I might as well throw the whole mess in the trash. What I'm gathering from this video is that you have to downgrade your transmitter back to the previous version whatever it was, and then do an update to the nano first over the air, before you update the transmitter firmware. So I did that, and then go back to the Nano firware screen and chose the latest update and click Update button and nothing happens. TBS needs to get their stupid sh1t together. There is no way I can go through this confusing mess with my eyes and my fat fingers.

[@mamodomo862]

I just dont believe in anyone advertising crossfire or expresslrs!!!? I have both and used lots of money to buy several recievers. this BL. crossfire is killing me. every time I have to bind to it and then next day I have to do everything all over again!!!?

[@edrone_]

Are you using the latest Agent M to update firmware? Do NOT use Agent X. I would highly recommend updating all your crossfire radios/modules and receivers to the latest firmware using Tbs Agent M.

[@krypt6679]

Same Problem Here bought a radiomaster pocket elrs and darwin fpv elrs drone and wont bind. Now I replaced the rx with a tbs crossfire nano and IT doesnt work too. So I ordert a crossfire external Module and if IT doesnt work im looking for another Hobby. It feeld like a scam to me. I did every Thing I have to Do but it doesnt connect to each other

[@srqcrna]

Downgrade upgrade downgrade upgrade just to freaking bind...

[@edrone_]

It all depends on the receivers firmware and your transmitters. Some versions don't get along. Let me know if I can help you if your still having issues.