(20-Nov-2021, 05:08 AM)Rob3ddd Wrote: I finally got mine to bind and update.
I used Agent M to flash firmware to Micro V2 first then receiver updated and binded.

Unfortunately as detailed in the posts above, using Agent M still isn't working for everyone. It still seems to be hit and miss right now and can involve many retries. Even then people aren't always ending up with a successful outcome. The only advice / solution at the moment is for people to just keep trying until they are either eventually successful, or until they have no hair left

(20-Nov-2021, 11:13 AM)SnowLeopardFPV Wrote: Unfortunately as detailed in the posts above, using Agent M still isn't working for everyone. It still seems to be hit and miss right now and can involve many retries. Even then people aren't always ending up with a successful outcome. The only advice / solution at the moment is for people to just keep trying until they are either eventually successful, or until they have no hair left

  The behavior is different during flashing firmware/updating/binding.
 I binded RX from agent M with power off to tx but usb plugged into module.
 
  Unfortunately I can’t remember the exact steps but it seems like I did everything while plugged into agent m.Updated and binded RX without turning on tx by using agent M.
 Unfortunately it was late and I read Agent M was needed and just sleep walked through the rest.

Man why I didnt read the entire thread?? Shoot got my new Nano RX and My old TX FW was like 2.93 which I have 6 quads binded with that FW.  Upgraded to 6.10 was a mess. Cant get anything to work. Same message everyone is getting SIGH

UPDATE: Ok fixed.  I didn't use the Agent X.. I used Agent M instead and make sure to use the latest fW version.

(20-Nov-2021, 10:16 PM)klnyc Wrote: Man why I didnt read the entire thread?? Shoot got my new Nano RX and My old TX FW was like 2.93 which I have 6 quads binded with that FW.  Upgraded to 6.10 was a mess. Cant get anything to work. Same message everyone is getting SIGH

UPDATE: Ok fixed.  I didn't use the Agent X.. I used Agent M instead and make sure to use the latest fW version.

Yes, people need to be using Agent M for any firmware updates, especially with the new chipset based receivers that can only run the 6.10 or later firmware. Some People were previously still having issues even when using Agent M but TBS might well have fixed the issue in that. In post #28 is a link where Trappy specifically mentioned to use Agent M because Agent X (still) has some known issues.

I think Agent M is the fix.
I updated 3 other older nano receivers today wireless in about a minute and flew a pack through each one.
There’s a short brief video by JB that if titled different may have presented solution to more pilots.
So does all this new firmware get crossshot working or is that betaflight 4.3?

For anyone who is having issues with a failed 6.10 firmware install even when using Agent M, try the following:-

1. Clear your browser cache using the "All Time" date range.
   
2. Downgrade the firmware to version 6.09 in Agent M.
   
3. Upgrade the firmware to version 6.10 in Agent M.
   

TBS have today made public the V6.12 (Beta) firmware for Crossfire and Tracer. Release notes for that new firmware version have now been added to the first post.

(11-Nov-2021, 10:01 AM)gokuhs Wrote: Hello!

I have the same "Reload Crossfire FW in Agent X" issue only in the new Nano Rx receivers labeled with "Min Version: V6.10" (with the old receivers i don't have this problem).

I have tried several things and none have worked. The emergency update and updating the TX several times, only from Agent X, from Agent M is impossible, it gives me "error 5" in different percentages. The only way I have managed to install it from Agent M is to Downgrade the TX to a lower version (in Agent X) and update with Agent M to 6.10, but the result is that it remains unusable, I have to enter bootloader mode and flash it again to make it work in Agent X.

So any one have more lucky with the new receptors?

At the end i update directly to version 6.12 with Agent X (with M is immposible). And all receivers are working well, inlcude the receivers labeled with "Min Version: V6.10"

(23-Nov-2021, 03:16 PM)gokuhs Wrote: At the end i update directly to version 6.12 with Agent X (with M is immposible). And all receivers are working well, inlcude the receivers labeled with "Min Version: V6.10"

Yes, the Agent X update issues are fixed in the V6.12 firmware update as specified by the second item on the release notes list...

• fixes update issues with Agent X for full-size TX, TX Lite and MicroTX
  

Hopefully people can now do any firmware updates they need to without having to bang their head against a brick wall.

Just updated most of my fleet pretty smoothly this time, using Asian X.

Hi people,
I just updated my Tango 2 to 6.12 and I got a problem. The calibration doesn't save.
6.10 works pretty good but when I update to 6.12 the gimbals stop working and I have to calibrate them every time I power it on.
Is somebody else having this issue?

Thanks!

(30-Nov-2021, 08:25 PM)SGr33n Wrote: I just updated my Tango 2 to 6.12 and I got a problem. The calibration doesn't save.
6.10 works pretty good but when I update to 6.12 the gimbals stop working and I have to calibrate them every time I power it on.

When you say everything works fine with the 6.10 firmware, did you try rolling back from the 6.12 firmware to 6.10 to prove that is still the case?

Did you also update the Tango 2 FreedomTX firmware to the latest version?

(30-Nov-2021, 09:19 PM)SnowLeopardFPV Wrote: When you say everything works fine with the 6.10 firmware, did you try rolling back from the 6.12 firmware to 6.10 to prove that is still the case?

Did you also update the Tango 2 FreedomTX firmware to the latest version?

I updated from the 6.07 to the 6.12 and I had gimbal problems.
Now I rolled back to  6.10 and looks that gimbals are working good.
With 6.12 I had no problems binding to a RX Nano receiver.
I also updated FreedomTX to 1.30.
Is nobody else having this gimbal calibration problem?

Thanks.

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 :\

Alright wish me luck.. Let me try Agent XXX :-P