It doesn't matter if it is a qx7 or x9 lite. If your quad is not getting into bind mode, it is an issue with the quad. Not the radio. If you are able get into bind mode, but the radio is still not binding. Then we can look at the radio.

You can also try the CLI method to get the FC into bind mode.

From oscar blog.

Connect the FC to computer, open Betaflight Configurator and go to the CLI tab
Enter this command to force FC into bind mode:
For Betaflight 4.1: bind_rx, BF4.0: bind_rx_spi, for BF3.x: frsky_bind
Enter save
The red blinking LED on the FC should now stop blinking
Activate the bind option on the radio
Wait a few seconds, then stop the bind function on the radio
Reboot FC, Done!

thanks all for trying. this was never solved. i returned the quad and now just watch mr. steele on youtube. too much time and money wasted.

(08-Jun-2021, 07:13 AM)grilled_cheese Wrote: thanks all for trying. this was never solved. i returned the quad and now just watch mr. steele on youtube. too much time and money wasted.

That's sad to hear.

If you ever decide to try again, get yourself a RadioMaster TX16S transmitter (or a TBS Tango 2) and invest in TBS Crossfire or TBS Tracer. Those systems "just work" and flawlessly, unlike the mess that FrSky created with their confusing ecosystem. FrSky are now to be avoided like the plague in this hobby. In my opinion.

... I honestly can say if it was not for YouTube and some forums I would have dropped this hobby like a hot potato... there is some seriously great information, that can take u way down the rabbit hole.. but it’s the small startup stuff that can get u lost before u know it.. simple like Frsky/Flysky.. Blheli S /32, betaflight / betaflight configurator.. just to name a few... and don’t get me started with “versions and firmware”...
It’s not “hard” per se, but it can easily confuse u and cause major frustration..

oh noo, thats sad to hear, frsky and their mess get you out of the hobby.
i hide any frsky product. i can just suggest, dont miss fpv pleasure because of frsky troubles, frsky is faraway the biggest issue in fpv; at least the mass of frsky-help-threads inhere does speak this language; you are not alone with this issues and frustration, there are other ways without such a mess.

I just found this thread and am trying to get this same combination to work. I tried several of the things in this forum, and different youtube videos, and also the instructions on the betafpv website and still can not get it working. At this point I'm not sure if the quad just isn't going into bind mode, or if I'm using a firmware on the taranis that's not compatible. I think verifying that the quad is getting into bind mode is probably the first step from here. I've reset everything using a cli dump from the betafpv website, and when I start the quad both the green and blue lights are blinking. Pressing the bind button seems to do nothing, also setting it to bind mode from the cli also doesn't change the flashing lights. Does anyone have any suggestions on what to try next?

Thanks!

After another night of tinkering I finally got it working. I ended up using different steps from a bunch of different sources and added a few of my own, so I don't know what actually fixed the problem. I'm going to post the steps here just in case someone else runs into this same problem.

Transmitter: FrSky Taranis X9 Lite
Quad: BetaFPV Meteor65 Acro

Not sure all of this is necessary, but after hours of messing around this is what worked.

1. Downgrade transmitter OS to 2.3.9 from FrSky website.
2. Get sd card version 2.3 v0029 from the open tx website.
3. Downgrade the transmitter ISRM RF firmware to 1.1.3 from the FrSky website.
4. Create a new model.
5. Use the following settings for Internal RF: Mode = ACCST D16, Ch Range = CH1-8
6. Connect the quad and run the betaflight configurator.
7. Go to the cli and dump the current setup to a file for safety.
8. Download BTFL_cli_SPI_Frsky_FCC.txt from the betafpv support website under "Manual for F4 1S AIO Brushless FC (SPI Receiver)"
9. Open this file in notepad and remove the lines with the following commands: set frsky_spi_autobind, set frsky_spi_tx_id, set frsky_spi_offset, set frsky_spi_bind_hop_data
10. Go to the cli in betaflight and enter the command "defaults nosave"
11. Import your modified cli file from step 9.
12. After the quad reboots go to the cli and type "bind_rx"
13. Select bind on your transmitter.
14. After a few chirps from the transmitter type save in the cli in betaflight and let the quad reboot.
15. Exit binding on the transmitter.
16. Profit?

As always back up everything before trying this. I'm not sure what part of this actually made it work this time, but I'm leaning towards removing the binding data from the cli and downgrading the isrm.