(25-May-2023, 12:22 AM)Angelsinterceptor Wrote: Hello all!
Please help me solve the problem, I can not figure it out myself for 24 hours (I am new to this hobby).

iFlight Nazgul Evoque F5 quadcopter, BETAFPV ELRS Nano TX transmitter (2.4GHz) on LiteRadio3, BETAFPV ELRS Nano receiver.

I updated the firmware on the receiver and transmitter to 3.2.1 through the ExpressLRS Configurator. I set up a way to communicate between them via Binding_Phrase. Trouble is, now when the quadcopter binds to the remote, it sends completely incorrect signals to it. Or I just don't understand what's going on.

In the BetaFlight Configurator on the "Receiver" tab, the drone is spinning like crazy and doesn't respond to stick and toggle switches. This happens exactly when the remote is on. If you turn it off, it stops.

That is, the quadcopter binds to the remote control, but then it all works completely wrong.
My controller is calibrated correctly and before updating RX/TX to 3.2.1 everything was working correctly.

I don't understand what the problem might be. I've been searching the internet all day and can't figure it out. If someone knows how to fix it, please advise.
Thanks in advance for the help and answers!

Change ATER to TAER? Or something like that? Sounds like that symptom. I get the same thing and I have to change this setting. Cause my TX is set off default.

(26-May-2023, 11:27 AM)Angelsinterceptor Wrote: Yes, I tried to switch now to 3.2.1 firmware exactly according to the guide from 2.5.2 But all the problems remained.
After that I tried to go back to 2.5.2 but now everything doesn't work either. The quadcopter binds, the blue LED lights up with constant light, but... There is no response to either stick or toggle switches in the Betaflight Configurator.

The only difference is that in 3.2.1 the quadcopter in the Betaflight Configurator rotates, but in 2.5.2 it just behaves as if there is no connection.

I tried reinstalling the firmware on 3.1.1 as well, tried doing it without the binding word, installed, returned but all to no avail. Nothing works now.

I am now in a very frustrated state. Yesterday everything was working and I was hoping to make my first flight on Saturday. Now I have no idea how to fix it. Apparently I'll have to take the quadcopter with the remote control and module to the service center, pay money and hope that everything can be fixed without rewiring the new RX module ...

I shouldn't have started touching things that work. I'll never fly like this...((

It's always the channel map.  Two of mine didn't use the standard map. Change it and move on.

But the other thing is if you have something working, why try to fix what isn't broken.  Especially if you know jack all about what you are doing.  Better to fly first, watch loads of tutorials on youtube, lurk on sites like this and learn as much as possible before you try and break your working drone.  The whole point of BNF drones is they are ready to use.  No need to update them.  They come from the factory ready to use. 

So don't intentionally start messing with them until you have an inkling of what the hell you are doing. Or in the worst case, curiosity killed the cat, which if you mess with settings on a 5" and did a flight test and it happened to fly into you at full tilt and sever your carotid, could be a very real end to things.

Don't fix what isn't broken.

Anyway, since you (and everyone else who seems to get into this hobby) have opened Pandora's Box, you have to learn to fix it now.  Best thing you can do is revert ELRS back to 2.5 and if you messed with Betaflight revert that too.  Get everything back to the starting point.  Follow any number of ELRS tutorials on Youtube.

Literadio 2 SE and the basic Literadio 3 only run ELRS 2.0.1, so you need some version of 2 on the Nazgul.  I use 2.5.1 on all of mine and it works fine.  Try it.  Setup your bind phrase.  Then go into Betaflight's Receiver tab and wiggle the sticks.  Make sure they all correspond to the correct mappings.  If not, write down what is set to what and change the channel map accordingly.  So try again, does everything work correctly now?  Yes, do a quick flight test and by that i mean go outside, get behind something, arm, hover, check it yaws, rolls, pitches correctly.  If all good, go fly and don't try and break it again until you know what you are doing.

To summarize what the problem was.
The Lite Radio 3 hardware is only suitable for flying on tinywhoop or in the simulator. It supports the maximum version of ELRS 2.0.1
The minimum version that can be build in ExpressLRS Configurator 2.5.2

On version 2.5.2 I had everything working, but through the external module BETAFPV ELRS Nano TX. But it worked on the word of honor. When I started to try again to switch to version 3.2.1 (which shouldn't and won't work on LR3 at all) there were some tails in the firmware and when I went back to 2.5.2 it stopped working too.

I did the following: 1) Completely cleared the flash memory of the external TX 2) Reflashed it via USB to version 2.5.2
So far this has solved the problem. And in the future I will be switching to RadioMaster Zorro.

I had a response, but I deleted it because I didn’t read your second to last sentence that said, “So far this has solved the problem.”

So, if you get an email notification with my response, ignore it.

Don’t touch anything else if it’s working.

And you should absolutely get a Radiomaster Zorro in the future.

TBH, the Literadio can be used for any quad in existence that uses ELRS. The version is the only limiter. But ELRS 2 works just as well as ELRS 3. As long as your rx has ELRS 2 (any version of), it should work fine. Whether it's a whoop or a 6", size is irrelevant, type of quad is irrelevant, the only relevant fact is the version of ELRS.

So ELRS 2 is not just for whoops, it's for anything you want to use ELRS 2 on.

Jumper T-Lite 2 will be cheaper and just as good as the Zorro. I have a T-Pro, but it's a bit more in-depth to setup.

When using the external ELRS TX module, are you setting Internal RF to Off and External RF to CRSF on your radio? It sounds like you may have had two TX active (both the internal and external ELRS TX) or just the internal TX active on ELRSv2 and the receiver on ELRSv3.

Are you flashing your TX module via USB or WiFi? What version was it on previously? Try flashing via USB following the guide I linked earlier. Updating from ELRS v2 to ELRS v3 via WiFi requires using the repartitoner.bin file as explained in the flashing guide. Show screenshots of the webui once you update to confirm the firmware version and binding phrase are set properly.

(26-May-2023, 07:27 PM)V-22 Wrote: When using the external ELRS TX module, are you setting Internal RF to Off and External RF to CRSF on your radio? It sounds like you may have had two TX active (both the internal and external ELRS TX) or just the internal TX active on ELRSv2 and the receiver on ELRSv3.

Are you flashing your TX module via USB or WiFi? What version was it on previously? Try flashing via USB following the guide I linked earlier. Updating from ELRS v2 to ELRS v3 via WiFi requires using the repartitoner.bin file as explained in the flashing guide. Show screenshots of the webui once you update to confirm the firmware version and binding phrase are set properly.

If I understand correctly, when the internal TX is active, the external TX is not even powered...
I tried flashing both via WiFi and USB. But now, until I buy new hardware, I'll leave the idea with the 3* version of ELRS.
Without repartitoner.bin file the firmware to version 3* from 2* is not possible. That is without this file an error will just go through and the firmware will not end. But it is enough to apply it only once.
With versions and binding phrases I checked exactly. In addition I flashed the same way and without the binding phrase (and binded through the triple connection and disconnecting the power). This did not solve the problem.

Hello, if it helps, 3 days ago I had the same problem as you, lite radio 3 and nano tx module from betafpv and in my 2 drones that I have the receiver tab reacts the same... after having tried everything, I have decided to buy a RadioMaster Zorro and I think the problem will be solved, since we can configure the lua script and more parameters in a simpler way