(01-Dec-2021, 02:46 PM)SGr33n Wrote: I found on Facebook a solution by Raphael Pirker. He said:
try downgrading to 6.10 and deleting your crossfire\eeprom file. that should force you to recalibrate and then it should "stick".

But even if for a user looks like this solved his problem, it's not the same for me, I'm still facing this issue :\

Unfortunately I don't have a Tango 2 so I can't really offer any further help. I suggest that you raise a ticket with TBS and they should then be able offer some alternative solutions to try.

Thanks, I will try.

Mah , in reality i not understand, 6.09 is stable, other are all beta. In you have new receiver you need 6.10 or more (all beta).
Ok, we have to install beta because works good , so why are still beta?
Lost some point of the story.
And ,if you fly for work too install a beta isn't a good idea.
In case of crash insurrence could not pay. Ok who check if you use beta or not? Probably nobody but ......if happen ....

Everything is beta in the hobby.

TBS have a policy to release a firmware as beta (but they are assumed fairly stable) and eventually they are flagged as releases after a few months.

I doubt any insurance agent has the time in the world to verify a crash was caused by beta firmware.

TBS "beta" firmware is actually release firmware. They just err on the side of caution by labelling it "Beta" firmware so that people have no ammunition to start throwing around if something does happen to go wrong. If you look at past TBS history of firmware, some firmware has remained at a "Beta" state for well over 6 months before getting promoted to a non-beta version. That sometimes involves them simply just removing the "Beta" label from an already published version rather than releasing a new revision without a Beta label on it.

TBS's real beta firmware is behind closed doors and is tested by a small army of sponsored pilots well before the general public ever get to even see a "Beta" version of the tested firmware appear on firmware update page.

The bottom line is that any firmware versions you see on the TBS Agent firmware update page are generally good for public consumption. The only reason I'm still on version 4.11 is because 6.x was a fairly major rewrite of some of the code base so I wanted to sit back and see what issues other people had first, and also because it is the winter season where I am so I haven't been flying for a few months. Now that the 6.x firmware has bedded in and most of the teething problems with flashing has seemingly been resolved, I will likely update all my gear to the latest version (even if that is a "Beta" version) just before I start to go out flying again in the Spring time.

Painless update using Agent X. Plugged in my Lite TX and updated to 6.12 then fired up The Ninja and set it to bind. It asked if I wanted to update the Nano RX, Yes and away it went. A minute later I was hovering it on POSHOLD with no issues. Too dark to fly right now, but everything seems to be in working order.

So it seems TBS has fixed the binding and firmware update issue.

(14-Dec-2021, 04:03 AM)kafie1980 Wrote: So it seems TBS has fixed the binding and firmware update issue.

It worked for me at least...would hope everyone experiences the same!  As the new RX's I received are truly the newer ones, it became a necessity to update.  Have now updated the RX's on Seven and The Drifter...no issues with any of the three so far.

Trappy made a statement on Facebook a few days ago that all AgentX related firmware update issues had now all been resolved and that TBS engineers could now finally get back on track by focusing their efforts on new enhancements and new features. I meant to post it on here but I forgot.

(14-Dec-2021, 03:01 AM)kaitylynn Wrote: Painless update using Agent X.  Plugged in my Lite TX and updated to 6.12 then fired up The Ninja and set it to bind.  It asked if I wanted to update the Nano RX, Yes and away it went.  A minute later I was hovering it on POSHOLD with no issues.  Too dark to fly right now, but everything seems to be in working order.

Have you tried updating any of your other RX's yet that are still on the 4.11 firmware? I'd be interested to know if you're able to use the "no bind button" method that TBS say you can, or if you have to resort to physically pressing the bind button on the RX's.

(14-Dec-2021, 10:35 AM)SnowLeopardFPV Wrote: Trappy made a statement on Facebook a few days ago that all AgentX related firmware update issues had now all been resolved and that TBS engineers could now finally get back on track by focusing their efforts on new enhancements and new features. I meant to post it on here but I forgot.

Here it is...

Source (Facebook): https://www.facebook.com/groups/BlackShe...3651304069

(14-Dec-2021, 10:35 AM)SnowLeopardFPV Wrote: Have you tried updating any of your other RX's yet that are still on the 4.11 firmware? I'd be interested to know if you're able to use the "no bind button" method that TBS say you can, or if you have to resort to physically pressing the bind button on the RX's.

Yes, those are the ones I am referring to. The referenced updates are all of my (previously) 4.11 RX’s. Did not require the button, everything is done through the radio. Hopefully your experience is as smooth as mine.

I know it can be done through the LUA script, but I just used the joystick on the back of my TX.

Crossfire / Tracer firmware version V6.13 has now been released.

NOTE: This version has replaced V6.12 that TBS have now entirely removed from the list of available firmwares which only usually happens if a firmware version was found to have some unacceptable bugs in it, so if anyone has already installed the V6.12 firmware on any of their devices they should immediately install V6.13.

EDIT: Firmware versions 6.07 and 6.09 have also disappeared from the available firmwares list, so if anyone has those version installed they are probably also best advised to update to either V6.10 or V6.13.

6.09 was a release and thats what I was flying.

They must have found something serious to take these versions off.

Yes, it does seem odd that they've removed what was the only non-beta 6.xx version. Trappy hasn't explicitly stated that people should upgrade from the V6.09 non-beta release if they have it installed, but there must be a good reason for them wanting to prevent anyone installing that firmware version from now on.

Im still seeing 6.07 and 6.09 in Asian X. 6.12 has certainly gone though, I noticed that a few days ago.
Anyway, I put 6.13 onto a couple of quads. All went smoothly.