TBS Crossfire Nano RX won't bind (Reload Crossfire FW in AgentX)
HTML-код
- Опубликовано: 11 ноя 2021
- Brand new Nano rx won't bind. This video walks through the situation and all of the steps I've taken to try and solve.
1. Binding with lua script on TBS Micro Tx in Frsky Tx results in blank screen
2. Binding with lua script on Tango 2 XF, results in error in title (flashing red & green)
3. Try to connect Nano Rx to Agent X, but is never recognized through my flight controller (is some additional a adapter a must?)
5. Binding with Agent X through Tango 2 XF, results in error in title (flashing red & green)
6. Binding with Agent M through Tango 2 XF, same result.
Is this Nano Rx not DOA?... It has surely wasted hours of my life!!
Please leave comment. I'll add the solution and an additional video if I get a solution that actually works.
![☀ Навороченный нано приемник + маяк от ТБС. Для серьезных парней. [Crossfire Diversity Nano RX]](http://i.ytimg.com/vi/hj1xBDP8UYY/mqdefault.jpg)
![☀ Навороченный нано приемник + маяк от ТБС. Для серьезных парней. [Crossfire Diversity Nano RX]](/img/tr.png)
Got it working! :)) Seems you have to get firmware V 6.10 on the TX (with Agent X) and then use Agent M (not Agent X) to RELOAD the firmware (V 6.10). Then, when trying to bind with this firmware in Agent M it will allow updating of the nano rx and they will finally bind! At least this worked with our hardware (TBS micro TX V2, nano rx, Agent M was used on a Mac with the Chrome browser).
Struggling now with this issue. 😅Let me follow your steps and see 🤞🏻
Lol. It's funny though, strange steps. But it worked for me too on a Windows laptop 😄. Thank you 🙌🏻 Saved me some time. 😬
@Richard Conway : Oops! :( I had done for another new quad (Evoque F5D) using RM TX16S on Edge TX probably around 8 hours ago and it had no issues at all. But this one on Evoque F5X using another RM TX16S on Edge TX few hours later gave this issue. Wonder why?!! But Tina's work around fixed the issue.
Thank you! This worked. I'll make an updated video with steps. I had done version 6.09 in Agent M with no luck, so the fix is clearly in the beta firmware. I wouldn't usually make that jump, but did it... and had to recalibrate my gimbals and everything... I hope all of my other quads are still bound. ¯\_(シ)_/¯ wha? ... fingerscrossed... Thanks again Tina!!
@@ScorpionFpv exactly why I made this video… I was at my wits end. Thanks Tina!
Just got same issue. Solution for me was simple - just update TBS Agent X to newest version :)
This was specifically during a time when TBS Agent X was not stable. Thanks for you comment and for watching.
Just to add, thank you both Tina and Steve - you're sanity savers!. I've been so frustrated with trying to bind this and have a stable connection when binding was finished. In the end I updated both the Tango2 & then the Tango2 XF using Agent M only.. it worked, I nearly started to change everything over to ELRS...
Works!! Thank You Tina! for the group I have a Tarranis Xlite Pro and the mini TX module. I updated to 6.10 FM on Agent X then ran the same firmware update on Agent M. When completed went to bind and it updated the Rx firmware. after the update the Rx light did stay red.. but when I went back to the main menu the light went green!! Spent weeks on this.. finally working!!
Again: i have the same problem. after the process i needed to recycle the power, then it was bind. But when i supply power to the quad, it takes about 6 seconds until the led turns green. On FW 4.x it was instant green. Did some video as well... ruclips.net/video/6WJWMWv48Lw/видео.html
Thank you for asking this question and for the community to figuring out the solution. A bit astounded there's no documentation on this from TBS. Crickets. Sounds like between us, we have tens or hundreds of hours spent on this. I've spent 4 on and off over the last 5 days. Come on TBS. Fess up and make this easy for people.
I followed Tina's suggestion and now have it working. I had two gotchas along the way. First one was I needed to upgrade my Agent X to be able to see the 6.10 version. Second one was I had to plug the TX into a different laptop and run Agent M from there. It wouldn't work properly on my other laptop though Agent X works fine on that laptop. Go figure.
Thank you Tina! The trick is to use Agent M (not Agent X) to load the firmware on the TX. Same set up, using Agent M on a Mac Mini with Chrome browser. The RX did not bind at the end of the process but then power off and power on again and it finally did bind. I spent so many ours on this. Thanks!
i have the same problem. after the process i needed to recycle the power, then it was bind. But when i supply power to the quad, it takes about 6 seconds until the led turns green. On FW 4.x it was instant green. Did some video as well... ruclips.net/video/6WJWMWv48Lw/видео.html
Can confirm that Tinas comment is exactly what worked! Sad that this is an issue needing to be dealt with for a Bind n Fly...
This worked for me. Upgrade your TBS crossfire firmware to v6.12 and everything will work like it should. V6.10 firmware does not solve the problem, you will get the same "reload crossfire FW in Agent X" warning. The only down side is, that you have to upgrade the firmware on all of your crossfire drone receivers (which is done automatically when turn on the drone) and rebind to the transmitter. Anyway, it's worth a try. Good Luck!
What firmaware versión do you have on the radio? I have 1.30 and is bro working
I followed the comments below - re-installing V6.10 via agent M, it then froze up at last binding step, so I had to unplug, restart and it worked!
TINA YOU SAVED ME!
same here with newer nano rx. works flawless with my 2 years nano rx ..
I got the same problem and struggle for 3 weeks. I had fixed it yesterday. The only problem is that after updating the firmware, you have to refresh the firmware by clicking the "Refresh" icon. Then, everything go smooth.
6.12 worked fine in Agent X without having to go through Agent M.
Just got an iFlight Nazgul Evoque and it was having your same issue.
What firmaware versión do you have on the radio? I have 1.30 and is bro working
hi, also had the problem on my 2 new Nano RX , solved with version 6.10 but
now with my old Nano RX I can binder but no more possible to set
receivers! on my TX16S I have the message that appears: "attempt to
concatenate field '?' (a nil value)"
it's work
Same problem here, but didn´t find much about it anywhere. Do you also have a V2 micro Tx?
I will be trying it with a V1 mcro Tx later..., for the friend I was helping with this quad. I hope the steps match and works the same. :)
reloading firmware in agent m kinda worked for me. it hung up at the end of the bind and I unpluged and replugged and it bound. not sure if I trust it
I was forced to re-bind all of my quad... If you have a chance factory reset all of your Rx before you do this solution, else you'll have to take the top off of everything that isn't easily accessible (that's 8 quads for me ¯\_(シ)_/¯ ). They're all up and running now. :-)
What size of power supply to chartreuse the dx3 do I need
Estava com o mesmo problema.
Foi resolvido com a versão 6.13.
Ok so what do I do on a qx7 doing that
Charger the power supply what size do I need
Hey so this worked,thank you, but now after the update and the RC is bind etc, Im no longer getting inputs on my tango and getting throttle warning anytime I turn it on. anyone had this issue ?
I have the same issue... after binding i have no inputs of throttle, yaw, pitch and roll. But other switches work. wtf?
@@enricfernandezantequera6397
so I recalibrated the sticks in the tango, but be careful, that shit, you may have to do it like 2/3 times, but it work, remember to check the TAER thingy in betaflight under receiver as well, so my tango is working , but it feels slow AF , the pitch and roll.
TBS should consider such mistakes like 6.10 for Tango 2 firmware.... I just waisted a lot of time and patience.... all my quads are disconnected now... WTF... the only binded, new cinelog does not react for stick input, switches work fine, what a move TBS...
I have the same problem, I was able to bind via agentM but now I have no stick inputs though my switches work 🤷🏼♂️
Using Tina's method exactly (above in the comments), I was able to bind to my new and old drones that have the Nano RX. However, I also have NO STICKS, just like Rafal. My switches work fine and when I flip those I can see a response on the screen of the Tango 2. BUT, when I move the sticks there is nothing. I even tried creating a new model and everything seems to be set up fine, but NO sticks. Anyone have any ideas how to fix that?
@@chrismcgowan6385 we’ve found it 💡and new Cinelog25 flies 🚀 The point is that we should calibrate Tango’s sticks after the update 😚🤭😌
@@RafalGalinski_drony PERFECT! Calibrating the sticks worked like a charm. For some weird reason that made them show up again (in Betaflight and on the screen of the Tango 2). Also, I had to use "Channel Map" in Betaflight to get the sticks in the correct order. Thanks for your help, Rafal!!! Can't wait to fly the Cinelog25... seems like an amazing little drone! I hope these posts help others that are having trouble.
@@LucyGoku Calibrate the sticks on your Tango 2 and they will show up again. Hope that helps!
mine yesterday wasnt bound i went to fly when the day before it worked perfectly fine and i didnt crash. im like why ...
Cost me a crsf tx lite, it went dead during update on agent M :(
i have the same problem. pleaseee the solution
Solution is Firmware 6.10 on your Tx, when using Tango 2 XF and Agent M to bind.
thank you very much everyone, it works yeeeeeeee
@@stevepeterson6851 Even in Agent M I still have pop-up "Reload Crossfire FW in Agent X", what i did without success
hallo bei mir hat es mir der Version 6.10 über AgendM geklappt
Agent x.
... maybe now, but 2 mo ago, no.