Sorry guess you are not having the bootloader issue in which case the pullup resistor would not solve your problem.

Have you checked the radio in the Betafpv configurator, are the stick movements showing up there and channels are correctly mapped? If you've already done that then maybe try the RX on another FC if you have access to one, to be sure its not the issue.

Yes in beta fpv I do have stick movements on my radio

Yeah of course I would have a difficult issue it's so crazy I don't understand what's wrong I've been at this for way too long trying to figure it out I just want to fly.

Maybe it appears to behave fine by that fact that it's not going into bootloader mode, but for your particular ELRS receiver it might still require a pullup resistor to work properly as mentioned by mstc.

I will try and ask around to see if there is any way re-apply Betaflight 4.1.7 to my FC with custom default settings getting applied automatically for the MATEKF411 unified target so that a "diff all" shows differences from the default MATEKF411 configuration settings and not from the base STM32F411 base firmware file. If I can do that I will happily try flashing Betaflight 4.4.1 to my FC to see if I then get the same issue as you on that Betaflight version. Unfortunately Betaflight 4.1.7 no longer appears in the firmware dropdown list on the flasher tab and I have tried versions of the Configurator all the way back to 10.5.1. In hindsight I guess I should have kept an offline copy of the original firmware HEX file but it's too late now.

Granted, the version of Betaflight shouldn't ordinarily cause such an issue but there may actually be a firmware bug in Betaflight 4.4.x for the GEPRC Stable F411 FC that is preventing an ELRS receiver from working properly. Or it may just be your particular ELRS receiver. If I can prove that it works on mine with Betaflight 4.1.7 (which it currently does) but not on Betaflight 4.4.1 we will then know there is some kind of issue / bug in Betaflight 4.4.1 for the GEPRC Stable F411 FC.

Thx for all your help, this is just frustrating me to no end, I really can't afford to throw more money at this project.

OK, so using an old spare flight controller I've managed to figure out for myself how to go back to an old unified version of Betaflight firmware that's not in the Betaflight Configurator dropdown list anymore, and still have Betaflight Configurator apply the required custom default settings. It turns out that you simply just need to download the appropriate base firmware file from GitHub (i.e. betaflight_4.1.7_STM32F411.hex) and then load that local file into Betaflight Configurator and flash it as per normal. Then when connecting for the first time, Betaflight Configurator still knows that there are some associated unified target settings available for the FC (I guess it just interrogates the board_name value from the firmware) and so it still prompts to apply the custom default settings. For some reason I didn't think it would do that when just flashing a base MCU firmware file. I'm glad I didn't ask on Discord or Facebook because I would have felt a bit stupid

So now that I know I can properly go back to Betaflight 4.1.7 on my GEPRC Phantom I will flash it to Betaflight 4.4.1 to see if my ELRS receiver still works under that version (or not). I will do that a bit later and report back my findings.

I just flashed the GEPRC Stable F411 FC on my GEPRC Phantom with Betaflight 4.4.1 using the default build options (shown in the image below), then I switched on "Serial RX" for UART2 and configured the receiver protocol to be CRSF. After doing that and plugging in a LiPo so I get a flashing green LED on the ELRS receiver, switching on my transmitter so I get a solid green LED (bound status), and then connecting a USB cable and running Betaflight Configurator I do see all the bars moving in the Receiver tab when I wiggle the sticks. So this confirms that there is no ExpressLRS specific issue or bug with Betaflight 4.4.1 running on the GEPRC Stable F411 FC because it is all working fine on mine with that Betaflight version.

I would try re-flashing ExpressLRS to both your ELRS module and the ELRS receiver. Make sure you have the "RCVR_UART_BAUD" and "RCVR_INVERT_TX" options NOT ticked.

If that doesn't fix the issue, try re-flashing Betaflight 4.4.1 using the default build options for the MATEKF411 target as shown below because I notice from your dump that your FC has some added/removed options from the defaults so go back to basics to eliminate any of those changes so you then have the same version and option as I flashed to mine.

Failing all of the above you might have a faulty ELRS receiver or one that requires a pullup resistor added to the circuit as mentioned by mstc in post #20.

(21-Apr-2023, 05:58 PM)SnowLeopardFPV Wrote: I just flashed the GEPRC Stable F411 FC on my GEPRC Phantom with Betaflight 4.4.1 using the default build options (shown in the image below), then I switched on "Serial RX" for UART2 and configured the receiver protocol to be CRSF. After doing that and plugging in a LiPo so I get a flashing green LED on the ELRS receiver, switching on my transmitter so I get a solid green LED (bound status), and then connecting a USB cable and running Betaflight Configurator I do see all the bars moving in the Receiver tab when I wiggle the sticks. So this confirms that there is no ExpressLRS specific issue or bug with Betaflight 4.4.1 running on the GEPRC Stable F411 FC because it is all working fine on mine with that Betaflight version.

I would try re-flashing ExpressLRS to both your ELRS module and the ELRS receiver. Make sure you have the "RCVR_UART_BAUD" and "RCVR_INVERT_TX" options NOT ticked.

If that doesn't fix the issue, try re-flashing Betaflight 4.4.1 using the default build options for the MATEKF411 target as shown below because I notice from your dump that your FC has some added/removed options from the defaults so go back to basics to eliminate any of those changes so you then have the same version and option as I flashed to mine.

Failing all of the above you might have a faulty ELRS receiver or one that requires a pullup resistor added to the circuit as mentioned by mstc in post #20.

Wow I appreciate all your hard work here I will definitely give that a shot and see if it helps any I kind of don't think it's going to I have Triton flashing but I couldn't do it betta flight passthrough

Just to clarify, the pullup resistor only solves the issue with going into bootloader mode at power on, but that is not your issue so it is not likely to help in your case. Did you ask on the ELRS discord, they are very helpful and maybe they have seen this issue before.

To reflash your firmware, do it over wifi not bf passthrough since you don't seem to have a working rx/tx link.

(21-Apr-2023, 07:57 PM)mstc Wrote: Just to clarify, the pullup resistor only solves the issue with going into bootloader mode at power on, but that is not your issue so it is not likely to help in your case. Did you ask on the ELRS discord, they are very helpful and maybe they have seen this issue before.

To reflash your firmware, do it over wifi not bf passthrough since you don't seem to have a working rx/tx link.

Okay got you right I'll do that over Wi-Fi and yeah you know what I haven't thought about asking on discord I'll have to look into that as well thank you. As far as the resistor goes I just ordered some just for future really anyways but yeah you're right it's not really going to help me in this situation cuz it doesn't go straight to bootloader when I plug it in. See after much thought I figured doing the resistor thing was just not going to help in any way just extra soldering that I don't really want to do anyway so I think I will try to reflash first over Wi-Fi of course and see if that doesn't help. After all that I think I will hit up discord and see what they have to say thanks for all the advice and I will keep you posted.

Before you go reflashing any firmware, another thought came to mind regarding your BetaFPV LiteRadio 3. You said in your first post that you have a BetaFPV Nano module in it. From this I assume that you have an external ELRS module plugged into the back of it.

Connect the LiteRadio 3 to your computer with a USB cable and run the BetaFPV Configurator, then check the following:

1. Ensure that the Internal RF module is switched OFF and that the External RF module is switched ON (if you are getting a binding with the ELRS receiver then it probably already is but double-check that anyway).
   
   
2. Wiggle the sticks and check that the bars for CH1-CH4 in the MIXES section at the bottom are actually moving when you do that. This will confirm whether or not the sticks are actually outputting any values over the air to the ELRS receiver. If not then the issue is with the transmitter (or configuration of the channels on it) and not the ELRS receiver.
   

(21-Apr-2023, 10:43 PM)SnowLeopardFPV Wrote: Before you go reflashing any firmware, another thought came to mind regarding your BetaFPV LiteRadio 3. You said in your first post that you have a BetaFPV Nano module in it. From this I assume that you have an external ELRS module plugged into the back of it.

Connect the LiteRadio 3 to your computer with a USB cable and run the BetaFPV Configurator, then check the following:

1. Ensure that the Internal RF module is switched OFF and that the External RF module is switched ON (if you are getting a binding with the ELRS receiver then it probably already is but double-check that anyway).
   
   
2. Wiggle the sticks and check that the bars for CH1-CH4 in the MIXES section at the bottom are actually moving when you do that. This will confirm whether or not the sticks are actually outputting any values over the air to the ELRS receiver. If not then the issue is with the transmitter (or configuration of the channels on it) and not the ELRS receiver.
   

I have done all that with success all sick movements good all switches as well, so I am all most positive it's not the transmitter. I'm a noob, but I've been troubleshooting for a while now. I am one of those people that hates bothering people for help lol.

So on my Literadio 2, I had an issue with the sticks not setting low when i powered up, ie, I never got the green light. So regardless of it being bound, it never had stick movement. So when i finally realised why, I worked out I had to pull the yaw stick to bottom right to make it think everything was set correctly. I don't think this is your problem, but if it is, you can bind it all day long and it will never give you stick movements in BF. Try slowly rotating the sticks and seeing if you get stick movement in BF and/or BetaFPV Configurator.

The other thing, which I assume you've done already is you need to calibrate the radio before it will allow you to use it.

So on mine I updated it to BetaFPV's firmware 2.0.1 and re-calibrated it, set the passphrase in the configurator and dealt with some small offset issues on the sticks. Ideally you will have the same version ELRS on your quad. So for me it was version 2.5 on the quad and 2.0.1 on the radio.

(22-Apr-2023, 02:51 AM)Pathfinder075 Wrote: So on my Literadio 2, I had an issue with the sticks not setting low when i powered up, ie, I never got the green light. So regardless of it being bound, it never had stick movement. So when i finally realised why, I worked out I had to pull the yaw stick to bottom right to make it think everything was set correctly. I don't think this is your problem, but if it is, you can bind it all day long and it will never give you stick movements in BF. Try slowly rotating the sticks and seeing if you get stick movement in BF and/or BetaFPV Configurator.

The other thing, which I assume you've done already is you need to calibrate the radio before it will allow you to use it.

So on mine I updated it to BetaFPV's firmware 2.0.1 and re-calibrated it, set the passphrase in the configurator and dealt with some small offset issues on the sticks. Ideally you will have the same version ELRS on your quad. So for me it was version 2.5 on the quad and 2.0.1 on the radio.

I get stick movement just fine in betafpv configurator, & transmitter has been calibrated correctly. Just not getting anything in betaflight. It is so frustrating, but thx for all the suggestions I won't give up yet.