I'm only getting signal from one antenna on my new BetaFpv diversity rx. Also, the firmware is detected as HappyModel, and when I tried to flash using the BetaFpv 2.4G diversity target, I got an error due to target mismatch.

I've written an email to BetaFpv support. I think I got it from Pyrodrone (it was awhile ago), so I might email them too.

Any other suggestions?

I want to get my quad flying again, and I get good signal from the one channel, so am thinking of just using it as is for now.

Try running ELRS LUA-script on your TX. Find "other devices" there and check diversity settings.

If you have the correct target selected, you can just click Force Flash, or check the "Force flash" box in ELRS Configurator.

How do you know you are getting signal only from one antenna?

Open the ELRS lua, go to Other Devices, select your receiver, and make sure the antenna mode is set to diversity.

(20-Oct-2023, 07:25 PM)lyoha Wrote: Try running ELRS LUA-script on your TX. Find "other devices" there and check diversity settings.

I don't see any diversity settings. Here's what I do on my TX 12, with rx connected:

1. Press SYS.
   
2. Select ExpressLRS.
   
3. Scroll down to Other Devices, and select it.
   

Here I only see:

Betaflight 4.4.2: S7X2 (highlighted)
BFPV SuperD 2G4
[----BACK----]

If I select SuperD, all I see is:

Tlm Power 100 mW (I can change this)
 [Loan Model ]
 [Return Model]
Model Id Off
3.0.0 8aa1b0
> Other Devices
[----EXIT----]

If this is what you're talking about, I don't see any diversity settings.

(20-Oct-2023, 08:06 PM)V-22 Wrote: If you have the correct target selected, you can just click Force Flash, or check the "Force flash" box in ELRS Configurator.

How do you know you are getting signal only from one antenna?

Open the ELRS lua, go to Other Devices, select your receiver, and make sure the antenna mode is set to diversity.

I tried that, and got a different error message. At that point I didn't want to mess it up even worse, since at least it works.

Here's what I do to check the signals on my TX12:

1. Press MDL
   
2. With my model selected, I page to page 10, TELEMETRY.
   
3. Scroll down to sensors, and I see:
   

1: 1RSS -26dB
2: 2RSS 0 dB

If I orient tx and rx antennas to match polarity, and move about 1m away, I see 1RSS -15 dB. If I move the rx antenna 90 degrees, the signal drops to about -30 dB.


2RSS doesn't change.

If I remove the antenna, the signal strength on 1RSS drops a lot.

If I connect both antennas, I get the same signal readings as before. If I orient the second antenna to match polarity with tx and rotate the other so it doesn't match, I get the same -30 dB reading as when only the one antenna was connected.

Swapping antennas doesn't change anything--I see good signal on the one channel and not on the other with either antenna.

With my other diversity receiver, I saw signals on both 1RSS and 2RSS.

As I replied to the other post, I don't see anywhere I can change any diversity settings, and again, I saw signal readings on both 1RSS and 2RSS with my other diversity receiver.

Here is what the ELRS web-based tool identifies the firmware as:

HappyModel EP Dual 2.4GHz RX

Firmware Rev. 3.0.0 (8aa1b0) ISM2G4

I don't know why a BetaFPV rx would come with HappyModel firmware when an ELRS target exists for this model rx, which is BetaFPM SuperD RX ELRS 2.4G.

At least the firmware has the word "Dual" in it, which I assume means it's for diversity.

Might want to update the RX. Antenna settings weren't added to that menu until later.

The HappyModel EP1 Dual and the BetaFPV SuperD use the same target, but the SuperD started shipping before the official target was added.

Update to ELRS 3.3.0 and you'll see the option in the lua.

(22-Oct-2023, 03:04 AM)V-22 Wrote: The HappyModel EP1 Dual and the BetaFPV SuperD use the same target, but the SuperD started shipping before the official target was added.

Update to ELRS 3.3.0 and you'll see the option in the lua.

TX is on ELRS 3.3.0. 


This is how I verify for TX:

1. Press SYS.
   
2. First page is TOOLS menu, at which I select ExpressLRS
   
3. Scroll to bottom of page, and see 3.3.0 ISM2G4 ae9df3. This verifies I'm on 3.3.0.
   

I also connected to the ExpressLRS web tool and verified the version as 3.3.0.

The RX firmware is 3.0.0. As I said, I've been unable to flash it with 3.3.0, even when checking Force Flash. With force flash, I get the following error screen:



Next I tried pressing the boot button on the rx until it started flashing a different color, and tried again to force flash. Same error.

Next I tried using WiFi. Successfully built the firmware using the BetaFPV target. Used the web tool to flash, and got a failure error with no options to force flash.

I'm stuck.

For grins, I also tried updating the SuperD rx to 3.3.0 using the HappyModel target, and got exactly the same error messages trying both with and without force flash selected.

I found that pushing firmware through the web browser page seems to work better when you need to force a flash. My Matek R24-D got stuck on the R24-S firmware somehow, and it would refuse everything until I tried that.

(24-Oct-2023, 04:38 PM)aerokam Wrote: TX is on ELRS 3.3.0. 


This is how I verify for TX:

1. Press SYS.
   
2. First page is TOOLS menu, at which I select ExpressLRS
   
3. Scroll to bottom of page, and see 3.3.0 ISM2G4 ae9df3. This verifies I'm on 3.3.0.
   

I also connected to the ExpressLRS web tool and verified the version as 3.3.0.

The RX firmware is 3.0.0. As I said, I've been unable to flash it with 3.3.0, even when checking Force Flash. With force flash, I get the following error screen:



Next I tried pressing the boot button on the rx until it started flashing a different color, and tried again to force flash. Same error.

Next I tried using WiFi. Successfully built the firmware using the BetaFPV target. Used the web tool to flash, and got a failure error with no options to force flash.

I'm stuck.

Can you post the rest of the error log? Are you following the flashing guide?
https://www.expresslrs.org/quick-start/r...assthrough

(24-Oct-2023, 07:55 PM)Suros Wrote: I found that pushing firmware through the web browser page seems to work better when you need to force a flash. My Matek R24-D got stuck on the R24-S firmware somehow, and it would refuse everything until I tried that.

Yes, I tried that too. I just did it again to grab screenshots. Here they are.

First, the warning about the target mismatch:




After proceeding, the failure message:



I note that building the firmware with the BetaFPV target (or HappyModel for that matter), results in the UNIFIED_ESP32_2400_RX target. I assume that this is what they both use, which relates to the earlier comment about BetaFPV and HappyModel using the same target.

(25-Oct-2023, 02:00 AM)V-22 Wrote: Can you post the rest of the error log? Are you following the flashing guide?
https://www.expresslrs.org/quick-start/r...assthrough

Well this is interesting ...

I had already looked at the log, and it was full of previous flash log entries. I wanted to delete it so we could just see the log for this flash attempt, so I deleted the log file. And yes, I have been following the ExpressLRS quick start guide in all of my flash attempts.

The rx was still in wifi mode (breathing green led) from the attempt to flash it from the web tool, and I left it that way to see what would happen. I opened the ELRS config program, selected the betafpv superdD target, and started the update (don't remember if I selected force flash or not -- I don't think so).

AND IT WORKED!

I now see that the firmware has been updated to betafpv superD 3.3.0, and I now see two rx options in the model -> other devices page on the TX: diversity and gemini. I now see signal on the second channel whichever one I select, but since the betafpv support guy said to use gemini, I'll use that. So apparently they shipped the rx without the firmware to support diversity or gemini.

Now I need to connect the second antenna.

Yay!

So, the two things that were different are that there was no existing log file, and the rx was in wifi mode. I never checked the mode before, but I'm betting it was not in wifi mode before, because I probably started the update process in less than 60 seconds.

I wouldn't have kept trying, and I wouldn't have tried the specific steps that seemed to somehow get it to work, if it weren't for the help from y'all here, so thanks much for that.

(26-Oct-2023, 03:57 PM)aerokam Wrote: I now see that the firmware has been updated to betafpv superD 3.3.0, and I now see two rx options in the model -> other devices page on the TX: diversity and gemini. I now see signal on the second channel whichever one I select, but since the betafpv support guy said to use gemini, I'll use that.

Nope, wrong call.

In reading up on gemini, I see that it requires two antennas on the tx; i.e., you need a gemini tx module. I just have the single channel internal ELRS that came with the tx12. OTOH, diversity works with 2 rx antennas and 1 tx antenna, so I changed the rx mode to diversity.

I went to a local park yesterday to do some quick tuning flights before connecting the second antenna, and with gemini set as the receiver mode. I kept losing signal with the quad not far away at all. I thought it was the monster power lines running over the park, but now I think it was having it in gemini mode. It worked fine with only one antenna before updating the firmware and changing the rx mode to gemini.

Here's how I've mounted the antennas: