TBS Crossfire- Emergency Update

6 Responses

  1. joe sagt:

    hello, I tried updating my micro diversity through the core pro bst and agent x with no success. on agent x I can only update to FW 2.07 beta and you say I need to be at least FW 2.09 for the core pro, what do I do? I also noticed your bst pinout for the cable is different from the tbs manual. is that correct?\
    thanks

    • KamiKatze sagt:

      hi joe,
      you are right – i got the scl and sda twisted. i’ll update it asap.
      The fw version was related to the fpvision. just use the latest (beta) version for the device to be safe.

  2. artyom sagt:

    hi. tell me please. I accidentally updated diversity nano rx through agent 2.4. now there is no bind. agent “x” has updated the transmitter to tbc. but there is no way to connect it. I am from Russia, no one has core pro / fpvision here. There may still be restart options. The option with clamping and fast blinking did not help.

    • KamiKatze sagt:

      hi artyom,
      sadly there is no chance without a core pro etc to get it back working.
      you can try to bind(with fw 3.9x or later) and as soon as the receiver will connect – unplug the rx battery. now retry. this CAN save it. but at the end of the day you’ll need a core pro etc to get it back. maybe you can finde one on ebay or cheap or send the rx back to your shop

  3. Allan Melo sagt:

    I had success with the emergency process update in a Micro RX V2 (couldn’t update by OTA at all), but no success with a nano diversity, I binded using version 2.24 in my transmitter, now it’ is bricked forerver, could you help me please ?

    • KamiKatze sagt:

      hi allan,
      in your case you need a core pro/fpvision/standard div. rx to get it back working.
      if your agent x (not the old one!) runns straight throu the update of the usb device, try swapping scl and sda

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.