I have a Mobula 6 Tinywhoop and a Jumper T Pro multiprotocol remote control with an external AIO ELRS module.
The ELRS module is set to 100 mW and 500Hz (I'm not sure what this means). On the Jumper T, I've set the "External RF" to "CRFS".

Settings on AIO ELRS module:
- ExpressLRS - Version: 2.5.1
- ExpressLRS TX expressLRS: 10.0.0.1
- Packet rate:  500 Hz
- TX power:  100 mW
- Telem ratio:  1:64 TLM

I don't think I'm doing anything wrong with the remote control, but the Mobula won't go into binding mode.

When I connect the battery, then disconnect, connect a second time, disconnect, and connect a third time, the drone should enter binding mode. This would be confirmed by a 2x green flash per second. However, the green LED on my drone only flashes once per second. The binding mode has not been reached.

An internet source https://brushlesswhoop.com/spi-bind-via-betaflight/ indicates that it is also possible to put the drone into binding mode via BetaFlight, but I don't have this button in my BetaFlight.

My BetaFlight never showed me the "Bind Receiver" button. I tried this with 3 different drones.


This is the receiver configuration:


This is my BetaFlight and Board version:


This is the CLI tab showing "status":



I tried tried to follow this tutorial: 
but CLI command line doesn't accept setting a binding phrase

Betaflight bind is only available for SPI receivers, not ones connected via serial. If you are on ELRS 3.x, probably easiest is to connect to the RX by wifi and set your binding phrase. Otherwise depending on your RX/firmware, plugging and unplugging the power 3 times may put it into bind mode.
https://www.expresslrs.org/quick-start/binding/

The triple disconnect to bind is the hardest thing I've encountered in this hobby so far ; ) It was harder to get into bind mode than it was to learn acro.
mstc was watching me try to do it and giving instructions and sufficed to say, we went with the wifi binding method in the end.

Personally I don't like the idea of plugging/unplugging battery unecessarily, but did that on a few serial AIOs and it worked on first try.
@Fpvme maybe your board came with a binding phrase already set, I think we saw something when we connected by wifi:

Notice
A Receiver flashed or set with a Binding Phrase WILL NOT initiate Manual Binding mode, however many times you try the procedure below. You must first reflash the receiver with the Binding Phrase field disabled and/or unset. Why would you not use a bind phrase though if you're already having to flash the RX anyway? ?

I'm a bit overwhelmed by the informations. How is it possible to establish a WIFI connection with the Mobula 6?

How do I find out what the current binding phrase is? Can I find this out via the BetaFlight CLI?

Once I have discovered the binding phrase, how can I input it into the "Jumper T Pro transmitter"? I've been researching on the internet for a long time and haven't figured out how to do it. Could it be possible that I only need to enter the binding phrase in the Mobula 6 and during the very first binding process, the phrase is transmitted to the ELRS transmitter?

Sorry, so many questions.

Sorry you're having so much trouble. I had a lot of trouble binding my Cinebot30 ELRS to my TX12 ELRS. Binding phrase did not work; I probably made some mistake. Pushing the boot or bind button did not work, and required partial disassembly; it was a real pain to put it back together.

The connect/disconnect 3 times worked for me, but the key was to turn off model match in the transmitter ELRS settings.

I never even figured out the lights, because all I saw was kind of a purple light, and I couldn't tell what lights were blinking. So I just went through the process without paying attention to the blinking lights, and it worked.

Now that I've torn it down, I see that there is a steady red light and blinking blue light on the AIO, which creates the purplish light I was seeing. There's another blinking light on the ELRS I think, but I've got everything disconnected now, so can't confirm. One light blinks for binding the tx to the rx, and another one for binding the goggles to the vtx.

Quote:The connect/disconnect 3 times worked for me, but the key was to turn off model match in the transmitter ELRS settings.

I've read that the binding mode (after plugging in the battery three times) is confirmed by the LED flashing twice per second. But somehow, I can't seem to reach this mode.

Quote:Betaflight bind is only available for SPI receivers, not ones connected via serial. If you are on ELRS 3.x, probably easiest is to connect to the RX by wifi and set your binding phrase. Otherwise depending on your RX/firmware, plugging and unplugging the power 3 times may put it into bind mode.
https://www.expresslrs.org/quick-start/binding/

Do I really have to flash my AIO module and the Mobula 6 with the Express LRS Configurator software? And which "devices" are the correct ones to be selected?

So, receiver and transmitter have to be the same major version. So ELRS 3.x and ELRS 3.x. Some Jumper T-Pro (at least the one I bought) shipped with ELRS 1. So first thing is to flash that to version 3. When you flash it, pick a bind phrase. Then go into ELRS Configurator again and flash the Mobula 6, with the same ELRS 3.x and put the same bind phrase in that you used on the radio. Now all being well, when you power up both they should automatically bind. if they don't then it gets a bit more complicated, but that's all I did on my original Meteor and it worked.

Follow this guide to update your TX module: https://www.expresslrs.org/quick-start/t.../#via-uart
And this guide to flash the serial receiver on your AIO: https://www.expresslrs.org/quick-start/r...r-firmware

If you have already flashed both to ELRSv3, you can set the binding phrase in the webui without having to reflash: https://www.expresslrs.org/quick-start/webui/

If you have any trouble, hop on the ELRS Discord and someone can walk you through it: https://discord.gg/expresslrs

I messed it up. This is not the Mobula 6, it is the Meteor 65 Pro (with the new ELRS v3.2.1).

I followed the steps to update my TX module from v2.5.1 to v3.2.1. In addition I set the binding phrase on both TX and RX.

Finally it's working.

Thank so much for all your help!

I went thru nearly 8 hours trying to bind to a ELRS SPI board before I found out I had to turn the packet rate down.

For all the hoopla from video reviewers it sure was alot of worki getting ELRS going...

(22-Jun-2023, 06:12 PM)Camaro6.2 Wrote: I went thru nearly 8 hours trying to bind to a ELRS SPI board before I found out I had to turn the packet rate down.

For all the hoopla from video reviewers it sure was alot of worki getting ELRS going...

I recommend always starting at the ELRS website if you have questions. 
https://www.expresslrs.org/hardware/spi-receivers/

And the ELRS Discord is the best place to get help if you are still having trouble: 
https://discord.gg/expresslrs

There is a huge difference in updating and binding the Mobula 6 and the Meteor6 Pro 2022.  The Mobula 6 has an SPI receiver.  The Meteor 6 Pro 2022 has a serial receiver.

For SPI you cannot use one of the D packet rates.  Set it to 250 Hz.  For updating you have to use BF.  For binding you have to use BF.  I had to do this with my Mobeetle 6, also SPI.  SPI receivers do not have wifi.

For serial you can still use a simple 250 Hz packet rate.  For updating the best way is to build a file with ExpressLRS Configurator, select wifi mode.  Then use the wifi method to update (serial receivers have wifi).  For binding use the 3 plug in method.  I don't use a bind phrase.  I did all this with my Meteor6 Pro 2022 and Meteor 7 Pro.  

I hope the manufacturers all stop putting out SPI receivers.