I have a BetaFPV Meteor75 Micro and trying to get it setup into my RadioMaster Zorro 4-1 but cannot get it to Bind....im showing the receiver as an FRSKY_D, unless that is not correct?

Thanks for any help!

There are a few versions of the Meteor75. I am not sure how to tell them apart. Anyways, if you have the Frsky SPI version of the drone, you can actually pick the Frsky D or Frsky X protocol from BFC.

There is also the ELRS and TBS Crossfire version of this drone, which will not work with your radio internal built-in protocols. Unless you get the external module.

ell I just received my new BetaFPV F4 1S SA Flight Controller / SPI Frsky board yesterday and have been trying to get it to bind to my RadioMaster Zorro 4-1 BUT still have not had any luck.....has anyone else been able to bind this FC with out having to use a BetaFPV module?

Here are the specs to the new FC.

Meteor75 / New FC:

F4 1S 5A AIO Brushless Flight Controller (SPI Frsky -V2.0 )  BMI270

version
# Betaflight / STM32F411 (S411) 4.2.11 Sep 29 2022 / 16:54:16 (norevision) MSP API: 1.43

board_name BETAFPVF411RX
manufacturer_id BEFH


I have attached a screen shot from BetaFlight:

According to Betafpv website, it should come setup with D16, but you can change it to D8 in BF if you prefer.
https://betafpv.com/products/f4-1s-5a-ai...8364789894

Quote:SPI Frsky RX
Come with the built-in SPI Frsky Receiver (CC2500 chip), F4 1S 5A AIO FC can be compatible with Futaba S-FHSS, Frsky D8, and D16 protocol. The default protocol is configured to Frsky D16 FCC out of the factory. Pilots could set up the protocol according to your own need in Betaflight Configurator.

Configuration Protocol
FRSKY_D          Frsky D8
FRSKY_X          Frsky D16 FCC (ACCST 1.X version)
FRSKY_X_LBT   Frsky D16 LBT (ACCST 1.X version)
SFHSS              Futaba S-FHSS

How are you setting the quad up for bind? Being that it is a SPI FrSky, you should be able to put the quad into bind mode using the phrase "bind_rx" in the CLI in Betaflight. One more thing to remember about FrSky is that they changed their protocol awhile back from ACCST to ACCESS. The TX from one will not bind with the RX from the other.