EDIT (15th April 2024): Added details for the new V6.33 firmware release.

NOTE #1: V6.13 replaced V6.12 which TBS 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 installed the V6.12 firmware on any of their devices they should immediately install V6.13 or later.

NOTE #2 (14th March 2022): V6.14 has now also been entirely removed due to binding and other issues. So if you are running that version, make sure you update to V6.16 or later.

NOTE #3: Be aware of the Public Service Announcement (HERE) that TBS have made regarding wiring of the telemetry data wire for any Crossfire / Tracer receiver.

TBS have just released new firmware for Crossfire which when used with a TBS Tango 2 or TBS Mambo transmitter reduces latency by ~1ms by bypassing the mixer for the 4 stick channels. This improvement only exists on those two transmitters, so anyone using a transmitter other than those two won't get that benefit.

Release notes for all Crossfire firmware releases are below in reverse chronological order. Some or all of these features & fixes also apply to Tracer as well but I don't have a TBS Tracer TX so I'm not able to see the release notes for that.

You should make sure you are on the latest version of TBS Agent X (downloadable from HERE), or alternatively use the web browser version of Agent M (HERE) which is always up-to-date.

NOTE: There is a new batch of Nano RX receivers fresh off the production line that are now using a different MCU compared to previous Nano RX's which has been done due to the global chip shortage of the original MCU's. The new MCU will only work with V6.10 or later of the firmware and there will be a sticker on the back of the Nano RX stating that if it contains that different MCU. Those newer Nano RX receivers have revision number "46" or later printed on the silkscreen of the circuit board.


Crossfire / Tracer (Combined) Firmware

V6.33 (Beta) [2024-03-23]

• Sixty9 and Fullsize TX issues fixes from 6.31
  

V6.31 (Beta) [2024-01-18]

• Re-release fixing previous Sixty9 and Fullsize TX issues
  
• Support for NanoRX Pro new hardware
  
• Added ch13-16 as selection to power switch and model ID selection
  
• Multi-bind works with any model ID (model ID no longer needs to be 00 for multi-bind to work)
  
• More information in the Update RX confirmation dialog. To be sure to update the right RX
  
• Optimizations and bug fixes in PPM input, expansion port, agent menu, smartaudio, FW updating
  
• PPM over Wi-Fi for Velocidrone Mobile
  

V6.27 (Beta) [2023-11-18] (release pulled due to bugs)

• Re-release fixing previous Sixty9 and Fullsize TX issues
  
• Support for NanoRX Pro new hardware
  
• Added ch13-16 as selection to power switch and model ID selection
  
• Multi-bind works with any model ID (model ID no longer needs to be 00 for multi-bind to work)
  
• More information in the Update RX confirmation dialog. To be sure to update the right RX
  
• Optimizations and bug fixes in PPM input, expansion port, agent menu, smartaudio, FW updating
  
• PPM over Wi-Fi for Velocidrone Mobile
  

V6.26 (Beta) [2023-11-01]

• Support for NanoRX Pro
  

V6.19 [2022-07-07] (promoted to a non-beta status on 2022-12-15)

When updating from below version 6.13, please perform a factory reset of your Crossfire TX after the update!

• Updated OTA protocol, working with newest Agent releases, to fix OTA issues
  
• Bootloader update for Micro TX, Fullsize TX & NanoRX Pro to fix bootloader-recovery issues
  
• Military-strength encryption of telemetry and PPM data (when enabled, multi-bind will not work anymore for obvious reasons)
  
• Direct-connection of uBlox GPS supported on Port 3/4
  
• Completely revised VTx handling (Sixty9, Unify Pro/Pro32)
  
• Faster pit-mode recovery for Sixty9 Team Racing
  
• CRSF V3 re-enabled
  
• GPIO output feature
  
• Minor bugfixes
  

V6.17 [2022-03-14]

• Disables CRSF V3 due to issues with some Betaflight FCs
  
• Fix: Premature Binding OK bug
  

V6.16 (Beta) [2022-02-23]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use v6.17

• Critical fix: Link statistics
  
• Fix: Autobind
  
• Fix: NanoRX (min.6.10) doesn't show GPS coordinates
  
• Minor: Flash both LEDs on power up / reset
  
• Minor: Commit hash in About
  
• Minor: Don't show RF Power in Diversity RX
  

V6.14 (Beta) [2022-01-04]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• Crossfire Nano RX Pro support
  

V6.13 (Beta) [2021-12-15]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• IMPORTANT: You may have to run the update twice (1x Update, 1x "Refresh"), as all update protocols have been revised and improved.
  
• Replaces v6.12 and 6.10
  
• Added baro sensor support
  
• Fixes update issues with Agent X for full-size TX, TX Lite and MicroTX
  
• Fix: Bug in Tango 2/Mambo configs storage in v6.12 (perpetual recalibration)
  
• Fix: Backwards compatibility of EEPROM.bin
  
• Resilient OTA updates with improved security
  
• Restored PWM channel maps due to popular demand
  
• Faster binding after OTA update
  
• Improve reliability of SD card on Tango 2 / Mambo
  
• Add idle-up to Gimbal Bypass mode for KiSS users
  
• Fix: MAVLink V1 issue in v6.10
  
• Fix: Binding issue after OTA update
  
• Minor: Fix for double pop-up during OTA
  
• Minor: New LED blinking patterns for OTA
  
• Minor: Ask users to reload fw in Agent M, not Agent X
  
• Minor: Tracer link stats fix for Betaflight OSD
  
• Minor: Multiple child firmwares in the SD cards
  
• Minor: Violet LED color on Tango 2 for validating firmware
  
• Minor: More responsive RGB LED
  
• Fix: Tango2 / Mambo random PPM pulse before startup
  

V6.12 (Beta) [2021-11-17]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• Added baro sensor support
  
• Fixes update issues with Agent X for full-size TX, TX Lite and MicroTX
  
• More secure OTA updates
  
• Improve reliability of SD card on Tango 2 / Mambo
  
• Fix: MAVLink V1 issue in v6.10
  
• Minor: Fix for double pop-up during OTA
  
• Minor: New LED blinking patterns for OTA
  
• Minor: Ask users to reload fw in Agent M, not Agent X
  
• Minor: Tracer link stats fix for Betaflight OSD
  
• Bugfix: Tango2 / Mambo random PPM pulse before startup
  

V6.10 (Beta) [2021-10-07]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• Feature: OpenTX mixer bypass for Mambo and Tango 2 sticks (AETR). Ch5-12 not affected!
  
• Feature: Improved stick calibration for Tango 2 & Mambo
  
• Feature: Team Race mode for all CRSF and SA VTx
  
• Feature: Auto mavlink and mavlink EMU handler
  
• Feature: Mavlink emulation over Wifi
  
• Improvement: More resilient Agent X / Agent M update protocol
  
• Improvement: Eliminate potential pitmode vtx interference
  
• Fix: Crossfire Diversity Nano Rx baudrate for serial 3 on
  
• Fix: Show readable user ID value after factory reset
  
• Fix: Team Racing and pitmode control improvements
  
• Fix: RX no longer losing sync after 25+ failsafes in short succession
  

V6.09 [2021-08-13]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• Team Race menu to quickly switch OpenTX model ID through switch 9 to 12
  
• SmartAudio control on output 1 and output 4 for Betaflight to control the Sixty9
  
• Improved pit mode control for video transmitters
  
• Fixed bug for video transmitter control not working on regular video transmitters
  

V6.07 [2021-08-04]

ATTENTION: Currently not recommended with Betaflight 4.3 RC1-3. Either use BTFL 4.2.x or use XF v6.17

• CRSF V3 & TBS Crossfire Sixty9 support
  
• Mambo release firmware
  
• Improved Mavlink routing (requires TBS Cloud v2.02)
  
• Fixed authentication bind bug on Crossfire
  
• Merged Tracer and Crossfire firmware
  
• Fixed all known Sixty9 bugs
  
• Revised MyVTX, now called "Video Transmitter" menu inside your transmitter settings with offline VTx configuration support
  
• Pitmode on a switch
  
• Crossfire & Tracer RF Power on a switch
  
• Implemented support for extended range R/C frames
  
• Stop sending link statistic frames when link is inactive
  
• Bug in 12 channel mode that leads to invalid first frame
  

Crossfire Only Firmware

V4.11 [2021-01-28]

• Improved: MAVLink stability
  

V4.10 [2021-01-27]

• Improved: Tango 2 performance in a cold environment
  
• Improved: MAVLink message routing
  
• Fixed: Turn on WiFI after re-enabling the RF
  
• Update: FLARM library
  
• Fixed: FLARM not showing up on glidernet
  

V4.08 (Beta) [2020-12-24]

• Fixed: Random TX reset which got introduced in V4.06
  
• Fixed: Constantly switching of CRSF flight mode
  
• Fixed: TBS GPS will make the Crossfire menu unable to load
  
• Improved: VTX control from TBS Fusion when VTX is connected via SmartAudio
  
• Improved: Minor fixes
  
• Tango2 1W
  

V4.05 (Beta) [2020-09-29]

• Added: Setting to enable/disable receiver internal voltage sensor
  
• Fixed: MAVLink bluetooth disconnection issue
  
• Fixed: CRSF telemetry to WiFi module
  
• Added: 500mW for Tango 2
  

V4.03 (Beta) [2020-09-15]

• Improved: Minor fixes
  

V4.02 (Beta) [2020-09-03]

• Fixed: Conflict of battery sensor when external and internal are present
  
• Fixed: Don't transmit invalid RC data at power up for Tango 2
  
• Fixed: Telemetry off feature
  
• Improved: Firmware update error messages
  

V4.00 (Beta) [2020-08-28]

WARNING! This update requires FreedomTX V1.21 or newer. Load FreedomTX first. Once loaded it will start the Crossfire bootloader immediately. Load Crossfire V4.00 or newer once the bootloader is detected inside the Agent X.

For more details see TBS Tango 2 product page

Required: Tango 2 needs to update FreedomTX 1.20 before updating crossfire

• Added: Up to 1W RF power for MicroTX V2
  
• Added: 250mW option for full size TX
  
• Added: WiFi driver for Tango 2
  
• Added: MAVLink over WiFi for all TX targets (requires WiFi V1.15 or newer / UDP Port 8888)
  
• Added: Dynamic VTX power support for SA VTXs (requires TBS Fusion
  
• Added: Receiver input voltage telemetry sensor added
  
• Improved: MAVLink library updated
  
• Improved: Internal code restructuring
  
• Fixed: Full size tx OLED joystick hold to modify float parameters
  

V3.78 [2020-08-21]

• Added: Up to 1W TX power for Micro TX V2
  
• Fixed: Bind issues for some units
  

V3.75

• Improved: Tango 2 keep gimbal calibration during factory reset
  
• Improved: Communication between FreedomTX and Crossfire
  
• Fixed: RGB issues on some targets
  
• Fixed: Tango 2 sensor lost warning when telemetry source is MAVLink
  
• Fixed: Various minor fixes
  

V3.72 [2020-06-01]

• Fixed: PPM stop outputting pulses for Failsafe Cut
  
• Fixed: Minor bug fixes
  

V3.71

• Added: Multi-Bind support
  
• Added: Tango 2, disable RF in USB Joystick mode
  
• Added: Tango 2, long press MENU and EXIT will reset region lock
  
• Fixed: Output mapping not being saved during power cycle
  
• Fixed: Don't reset region setting during factory reset
  

V3.54

• Improved: Merged all changes from V2.28
  
• Improved: Menu load speed for full size TX
  
• Improved: Lowered RGB brightness for Tango 2
  

V3.53

• Added: Tango 2 support
  
• Based Version: V3.25
  

V3.28 [2020-02-04]

• Added: CRSFshot support
  
• Added: Wake WiFi module up from sleep
  
• Fixed: Douplicate RC frame when more than one port is set to CRSF
  
• Fixed: Channel Mapping Menu
  
• Fixed: Power warnings when above the allowed maximum for the selected source
  

V3.23 [2019-09-26]

• Added: Renewed menu based on CRSF parameters
  
• Added: CRSF menu editor to change settings of other CRSF compatible devices like Unify Pro32, Unify Evo ect
  
• Added: MyVTX / VTX settings can now be set on the Crossfire TX and will be sent to the quad as soon as the connection is up
  
• Added: Power based LED color for race directors
  

V3.00

• Added: 868 and 915 race band for region open (double the RF hopping channels)
  
• Added: Ability to force RF to 150Hz
  
• Added: RF profile selection: Dynamic (switching dynamically between 150Hz and 50Hz), force 50Hz and force 150Hz
  
• Fixes: Don't show Bluetooth settings for TX LITE
  
• Fixes: MAVLink capacity used glitch
  
• Fixes: Swapped names for BST SCL and SDA output mapping
  
• Fixes: Only auto-bind to previously bound TX
  
• Improved: Telemetry bandwidth limiter
  

V2.94

• Added: Ability uppload commands and heartbeat from GCS to UAV using MAVLink in 50Hz mode
  
• Fixed: LUA Scripts running through nano diversity output 1/2
  
• Fixed: MAVLink telemetry jitter in 150Hz mode
  
• Fixed: RC over MAVLink menu selection for all MAVLink ports
  
• Fixed: Nano and Micro RX not able to boot for certain output mapping
  

V2.93 [2019-02-20]

• Added: SmartAudio V2.1 support
  
• Added: Nano Diversity support
  
• Added: SDA and SCL pin of Micro V2 and Nano can be used as PWM channel
  
• Added: SmartAudio driver for diversity receiver
  
• Added: Diversity ouput 3/4 can be used for MAVLink, CRSF, SBUS, SmartAudio
  
• Improved: Dynamic power
  
• Fixed: Sensor lost message
  

V2.42 [2018-10-18]

• Added: 250mW RF power option for micro TX
  
• Added: DSMX support for diversity (Output 8), micro and nano (Output 1) receivers
  
• Added: GPS speed and heading added to OpenTX telemetry stream
  
• Added: Ability to unlock up to 2W RF power if CROSSFIRE is powered from RC or HT port.
  
• Fixed: Hide FLARM settings for micro and nano receiver
  
• Fixed: Show RC over MAVLink option for nano receiver
  

Downloaded the updated Agent the other day and noted the 6.10 firmware. Still running 4.x on all of my RX’s after seeing folks having a few issues with the latest releases. Is it a good idea to update if everything is working currently? I have had no problems with the 4.x firmware.

I had to go 6.09 because I put a Crossfire Sxity9 on my latest build and had to upgrade 4 other quads with Nano RX's.

Upgrade was a pain from 4.x to 6.09 because all my Nano RX's lost binding with the TX.

On 3 Nano RX's I had to run emergency update first, then bind and finally update them to the latest firmware.

Firmware update/binding issues aside, they fly just as they did on previous 4.x versions. So far so good and I have been flying them for several weeks now.

I don't normally hold back with updating my Crossfire gear with the latest beta versions of firmware but I've read about enough issues some people have had with the 6.x firmware to make me nervous about upgrading, so this time I've just remained on the 4.11 firmware. I don't have any Sixty9's or any of the newer Nano RX with the changed chipset that requires the 6.x firmware, so I have no need to update anything just yet.

One of the biggest risks with the 6.x firmware is that TBS merged the Crossfire and Tracer source code together so that they now only have one code base to maintain for both systems. Doing something like that is not a trivial task and is always fraught with issues and teething problems. I'm sure it will come good eventually but I think I will probably wait for a few more iterations and confirmed stability before I make the jump. Unless of course someone has a very strong argument to convince me otherwise.

That is my feeling on it as well. There does not appear to any compelling addition that would be an “update” for the way my system is set up. I did receive a spare RX that I ordered a while ago and it is a “45” series instead of the “43” series that the rest of them are. Need to check to see if it is part of that new batch. As it is allocated to any aircraft at this point, so if it is, I will just leave it be unless I actually require it.

I have not seen any detailed images of the new Crossfire Nano RX with the updated chipset.

Trappy did mention on the TBS livestream that the updated Nano RX’s will have a sticker on the back mentioning that the firmware needs to be updated to 6.10.

So if you don’t have a sticker then we can safely assume you do not need to update your setup to anything over 4.x.

Hello Guru's,
  I received a new crossfire nano receiver, on the back of the package it reads "Min Version: v6.10".  So, I updated my Crossfire Micro TX module to 6.10 and then updated all other kwads' rx's to 6.10 with no problems.  I cannot get this new receiver to bind.  I've tried using Agent X and the crossfire lua script on my Taranis X9d+.  Either method, I get an error message saying "Reload Crossfire FW in Agent X."  I've reloaded the firmware three times, the binding process fails.  I then tried to apply the "emergency bind" procedure and after the receiver loads the "golden fm" and I try to bind it, I get the same "Reload Crossfire FW in Agent X" message.  I've opened a ticket with TBS thursday but still haven't heard back.  Anyone have advice how to fix this?

(30-Oct-2021, 11:54 PM)cpintheloop Wrote: I cannot get this new receiver to bind.  I've tried using Agent X and the crossfire lua script on my Taranis X9d+.  Either method, I get an error message saying "Reload Crossfire FW in Agent X."  I've reloaded the firmware three times, the binding process fails.  I then tried to apply the "emergency bind" procedure and after the receiver loads the "golden fm" and I try to bind it, I get the same "Reload Crossfire FW in Agent X" message.  I've opened a ticket with TBS thursday but still haven't heard back.  Anyone have advice how to fix this?

Try loading the firmware in Agent M instead of Agent X to see if that resolves your issue...

https://www.team-blacksheep.com/agentm

(31-Oct-2021, 01:46 AM)SnowLeopardFPV Wrote: Try loading the firmware in Agent M instead of Agent X to see if that resolves your issue...

https://www.team-blacksheep.com/agentm

That method resulted in the same outcome.  Thanks for your suggestion, SnowLeopardFPV.

I have mot had a chance to play with the new Nano RX’s with the updated chip.

Did you try Agent Lite on your Transmitter? Is your Crossfire TX showing the correct version?

I had the "Reload Crossfire FW in Agent X" message 2 or 3 times when trying to update my fleet to 6.10. I tried reloading the firmware onto my Tango 2 a couple of times with Agent X, then finally everything went smoothly.
I've no idea what caused the hickup, but everything is good now.

I notice today there is yet another update for Agent X, to v3.0.51. Might have something to do with the above mentioned gremlin?
Who knows!? Theres no release notes..?

I had the exact same thing happen to me as well. Got a new nano rx just 3 days ago and could not for the life of me bind it. Shows green on tango then goes to blue led saying reload crossfire tx firmware. On rx flashes green then solid red. The way i was able to successfully bind it was : prior to download sd card contents from https://www.team-blacksheep.com/tango2_s...7_0026.zip. then back up your sd card 

.now put tango in sd card mode and delete old sd card and transfer new sd card 1.2x make sure its unzipped first. disconnect then reconnect now go to agent x. 

1.Download newest version Agent x; Agent m kept freezing during binding at 96% :
2.flashing newest firmware of freedom tx 1.31 or under tango 2 newest under firmware. Dont click on a new window or search the web while updating dont ask why but it work. Wait for all the checkmarks to finish they will even tho you think it freezes just keep scrolling mouse wheel for some reason it keeps it moving along:
3. flash tango 2 tx or crossfire micro tx same thing, with version 6.10 and do same thing by staying on same window and just keep scrolling up down every lil bit if u have freezing issues.

4. disconnect tango from usb and power cycle. 
5. find agent lite on tango and click bind then put aside while its searching.

6. move to your nano rx and power on while holding bind button then release it putting it into bind mode. 
7. once its in bind mode flashing green rapid, hold the bind button again until you see it go through series flashes then it turns solid green then you release bind button. it will eventually go back to normal binding flashes. unplug then plug back in regularly.

if your radio doesnt pick up binding right away, exit the bind and rebind it will eventually ask you to update nano rx and bingo. 

for some reason it only worked through agent lite for binding and flashing nano. it froze everytime in agent x and m when i tried binding freezing in the firmware update of nano resulting in starting over step 6. So without rambling to much follow this and you will get it to eventually flash nano with new firmware and bind successful.

Yikes! And I thought I had a rough time! Thankfully for me, after agent m froze during one of my attempts, I went back to agent X and it finally worked.

Thanks for the detailed directions, kreativefpv!

I have the new version of Agent M on mac and PC tried Agent M and still cannot bind this quad without getting this: Reload crossfire fw agent x.
Diatone Roma L5.

I actually removed Agent X from my TX, removed the crossfire and contents from the Radiomaster TX16 SD card did a fresh install without Agent X and still will not bind. Tried agent m again on both pc and mac running chrome and it will not bind.

Yes I have done the emergency recovery numerous times during the past two weeks and nothing.

I have a ticket in with support but in the meanwhile, can anyone suggest anything that I have not tried on this thread and the other thread with this issue.