I've jumped through a hoops for a bit now trying to find decent documentation on all this, but so far i've yet to have any luck.

I have maanged to-

1. Connect the meteor65 to betaflight.  I saved the initial setup.  From what I can tell the relevant dropdown is the channel map, which is currently set to TAER1234.  This is from the "spektrum" setting, but I can also choose Frsky (AETR1234) and default (Same thing).

2. Connect the controller to OpenTX.  From there i didn't do much, but I did note that the default seems to be TAER...however i'm not sure what mode its in.

The documentation is sparse to say the least, and also seems to be out of date.  I attempted pushing the bind button on the back of the transmitter and then on the flight board (with the battery in), but it doesn't seem to do anything (and is tricky to do in time).  Lots of stuff mentions a flashing green LED, but mine is blue instead...?

I can't find any real examples of someone binding this, as most of what i find just seems to assume you know how to do it, or is for a vastly different transmitter which makes me think i'm missing something.

Oh and before i forget the LiteRadio instructions do mention switching protocol by holding the Bind button and then "pressing" the power button until the purple light is flashing and then counting the number of flashes to determine what mode you're in. I can't get this to work at all, trying different combinations of press/hold.

Edit-

Still can't get it, but found a few more things-

1. I may have been looking at the wrong betaflight setting? I found the reciever section under configuration. It's set on serial-based receiver with CRSF as the provider, however I can't seem to change it, as save and reboot just reboots with the same setting?

2. There is another button on the underside of the whoop that does trigger a green LED, however I think this is connected to the camera. The red/blue LED's button has the letters PNP above it, the red/green, nano. Of note the red/green seems to be on a totally different chip which is sitting below the board/above the battery holder.

Edit 2-

I believe the mistake was made when ordering. Looking at the drone I think this is a TBS crossfire version, not the FrSky...which would explain the inability to pair. Not sure how to even proceed from here. I guess I either get a new transmitter or swap the receiver. Both seem much heavier than I was hoping for a first try though.

Can you post photo of your antennas? Crossfire antenna is a T. While the Frsky antenna, you will not see it.

To add to what Voodoo said, if it has an "crossbar" type antenna sticking out of the back which looks like the following then you have a TBS Crossfire receiver in your BetaFPV Meteor65, which is why it won't bind to the BetaFPV LiteRadio 2.

did you ever figure this out? I'm having the same issue

As @SnowLeopardFPV mentioned, make sure you have the proper receiver on your Meteor65.
I have the Beta85X myself and LiteRadio 2 and they bind almost out of the box. Just have to set LiteRadio to Frsky D16 LBT in my case, cause my Beta85 has the XM+ LBT receiver.
LiteRadio 2 comes in two flavors, or FrSky or Bayang (toy quads protocol). From your comments it's clear that your LiteRadio is FrSky. So yep, wrong receiver on your Meteor.
Unfortunately you can't add a TBS module to the LiteRadio 2. If you were to have a Taranis or similar, you could have upgraded it with a TBS module, and problem solved.
So if I'm right, you have 2 options, unless just simply returning the quad is an option too, obviously.
-Get a Frsky reveicer and change it on your quad.
-Get a TBS capable radio.

(30-Oct-2020, 04:49 PM)ronyperez Wrote: As @SnowLeopardFPV mentioned, make sure you have the proper receiver on your Meteor65.
I have the Beta85X myself and LiteRadio 2 and they bind almost out of the box. Just have to set LiteRadio to Frsky D16 LBT in my case, cause my Beta85 has the XM+ LBT receiver.
LiteRadio 2 comes in two flavors, or FrSky or Bayang (toy quads protocol). From your comments it's clear that your LiteRadio is FrSky. So yep, wrong receiver on your Meteor.
Unfortunately you can't add a TBS module to the LiteRadio 2. If you were to have a Taranis or similar, you could have upgraded it with a TBS module, and problem solved.
So if I'm right, you have 2 options, unless just simply returning the quad is an option too, obviously.
-Get a Frsky reveicer and change it on your quad.
-Get a TBS capable radio.

Hey @ronyperez, I'm struggling to bind the Beta85X V2 with the LiteRadio 2.
I've changed LiteRadio 2 to Frsky D16 FCC, I put put it into binding mode then I try to put the quad in binding mode but I must be doing something wrong because the lights won't flash.
Doesn't the Beta85X V2 come with the FrSky XM+ receiver?
Sorry for the newbie questions but i'm totally new to this.

(17-Nov-2020, 06:59 PM)andrezinh0 Wrote: Hey @ronyperez, I'm struggling to bind the Beta85X V2 with the LiteRadio 2.
I've changed LiteRadio 2 to Frsky D16 FCC, I put put it into binding mode then I try to put the quad in binding mode but I must be doing something wrong because the lights won't flash.
Doesn't the Beta85X V2 come with the FrSky XM+ receiver?
Sorry for the newbie questions but i'm totally new to this.

I think I'm having the exact same problem... I ordered a meteor65 and selected the XM+ receiver, which I assume to be the SPI Frsky D16 FCC.. sound right?  The FC would be this model

https://betafpv.com/products/f4-1s-aio-b...Hs4JUG95u0

I can't seem to get the FC into bind mode... I've tried long pressing the button, short-pressing, multiple presses, pressing then installing the battery, and NOTHING seems to put it in bind mode (not even using the CLI in betaflight).

The only way I've resulted in a different LED pattern is by putting it in bootloader mode (pressing button before installing batter). I even tried binding the transmitter in this way and nothing...

How the hell do I put it in bind mode?! :/ Sooo frustrating

(18-Nov-2020, 10:50 PM)soma5eeker Wrote: I think I'm having the exact same problem... I ordered a meteor65 and selected the XM+ receiver, which I assume to be the SPI Frsky D16 FCC.. sound right?  The FC would be this model

https://betafpv.com/products/f4-1s-aio-b...Hs4JUG95u0

I can't seem to get the FC into bind mode... I've tried long pressing the button, short-pressing, multiple presses, pressing then installing the battery, and NOTHING seems to put it in bind mode (not even using the CLI in betaflight).

The only way I've resulted in a different LED pattern is by putting it in bootloader mode (pressing button before installing batter). I even tried binding the transmitter in this way and nothing...

How the hell do I put it in bind mode?! :/ Sooo frustrating

Did you ever get this to work? I'm having the same problem - I cannot get the Meteor65 FC (F4 1S AIO FC) into bind mode.