expressLRS

Hi i have tested the last version everything works good. The only problem i have is that the module restart all my settings when i reboot the transmitter. Rate. Telemetry power etc... any idea ?

I have betafpv 1w tx betafpv rx elrs 2.2.0
Thanks !

Hi, I'm sorry I am not giving feedback anymore.
I have family in Ukraine and busy getting them out. Not that I can do much but ok.
flew once this week and seemed to work fine and smooth.

mooiweertje wrote: Hi, I'm sorry I am not giving feedback anymore.
I have family in Ukraine and busy getting them out. Not that I can do much but ok.
flew once this week and seemed to work fine and smooth.

No worries. Hope your family stays safe and whole.

LAM_FPV wrote: Hi i have tested the last version everything works good. The only problem i have is that the module restart all my settings when i reboot the transmitter. Rate. Telemetry power etc... any idea ?

I have betafpv 1w tx betafpv rx elrs 2.2.0
Thanks !

Interesting! I had not noticed this behavior before but I think it's consistent with the description on the ELRS Model Matching page . If your model's Fixed ID is outside the range 0(None)-63 then this explains the behavior you're seeing. I can duplicate the behavior on my HappyModel ES2400TX.

For Fixed IDs from 0-63 (Deviation displays 0 as None) the ELRS Model Matching feature is in effect. The doc at the link above says that even if the Model Match setting is Off, ELRS stores some parameters based on Fixed ID, with up to 64 sets of parameters. For Fixed IDs outside that range ELRS boots up with the default parameter settings.

Try changing the Fixed ID to something in the range None-63 for each of your ELRS models. It's fine to use the same Fixed ID in multiple models if you don't use Model Match and do want the models to use the same ELRS parameter settings.

Also want to mention there is a fix in ELRS master branch that may also be needed, though if the Fixed ID change works then the ELRS fix will only help the menus load faster. The ELRS change will be included in the 2.3 version.

WOW ! proud to say that now everything works perfectly ! My problem was an fixed ID problem. I put 1 on fixed ID and now everything is OK ! Thank you so much !

It seems like 400k and 1.87M bitrate work well, wich one do you advice to use ?

Ok for the 2.3 i will flash it as soon as it will be released !

Testing on 2.4g with eLRS 2.2. latest deviationTX build linked above.

Connection defaults to 150hz which is not correct for 2.4g systems, every time I put in a new pack the connection is set to 150hz.
Anytime the RX restarts the TX is defaulting to 150hz, I believe the prior packet rate should be retained (as on EdgeTX).

belrik wrote: Testing on 2.4g with eLRS 2.2. latest deviationTX build linked above.

Connection defaults to 150hz which is not correct for 2.4g systems, every time I put in a new pack the connection is set to 150hz.
Anytime the RX restarts the TX is defaulting to 150hz, I believe the prior packet rate should be retained (as on EdgeTX).

Sounds like the same thing as described in my previous post. Change your model's Fixed ID to 63 or less. ELRS saves some TX settings even when not using Model Match, but only for model id's 0-63. For CRSF Deviation treats any Fixed ID over 63 as 255. ELRS treats this as "no model id defined" and doesn't store settings in that condition.

I see that EdgeTX only allows the model id (Receiver) to be set 0-63, so it's never the "off" value. That's probably a good UI choice. There may be some users that want to change settings but not have them saved past the current power cycle. But judging by these two questions it seems mainly to cause confusion. I'll think about a change.

Maybe just lower the value to 63 when elrs is selected? Is not ideal but works and is less confusing.

Thanks, confused as to why model ID was in play, thought it was left as default... Guess default is not 0 like I expected.

hexfet wrote:

LAM_FPV wrote: Hi i have tested the last version everything works good. The only problem i have is that the module restart all my settings when i reboot the transmitter. Rate. Telemetry power etc... any idea ?

I have betafpv 1w tx betafpv rx elrs 2.2.0
Thanks !

Interesting! I had not noticed this behavior before but I think it's consistent with the description on the ELRS Model Matching page . If your model's Fixed ID is outside the range 0(None)-63 then this explains the behavior you're seeing. I can duplicate the behavior on my HappyModel ES2400TX.

For Fixed IDs from 0-63 (Deviation displays 0 as None) the ELRS Model Matching feature is in effect. The doc at the link above says that even if the Model Match setting is Off, ELRS stores some parameters based on Fixed ID, with up to 64 sets of parameters. For Fixed IDs outside that range ELRS boots up with the default parameter settings.

Try changing the Fixed ID to something in the range None-63 for each of your ELRS models. It's fine to use the same Fixed ID in multiple models if you don't use Model Match and do want the models to use the same ELRS parameter settings.

Also want to mention there is a fix in ELRS master branch that may also be needed, though if the Fixed ID change works then the ELRS fix will only help the menus load faster. The ELRS change will be included in the 2.3 version.

That seems reasonable and is easier than making warning dialog. I am curious why ELRS has the feature of not storing settings if model id is 255 (or maybe anything over 63). I'll look at that code's history.

New test build is available - 5889e07 . This build sends a model id of 0 to ELRS if the Deviation Fixed ID is greater than 63. I'll probably make a change to the UI so it's only possible to set a CRSF fixed id in the range 0-63 but UI changes take more time.

From looking at the ELRS code I learned the situation is a little different than what I thought. The fixed id of 255 meaning model match is off only applies to the RX. When sending a model id to the TX it should always be in the range 0-63.

hexfet wrote: New test build is available - 5889e07 . This build sends a model id of 0 to ELRS if the Deviation Fixed ID is greater than 63. I'll probably make a change to the UI so it's only possible to set a CRSF fixed id in the range 0-63 but UI changes take more time.

From looking at the ELRS code I learned the situation is a little different than what I thought. The fixed id of 255 meaning model match is off only applies to the RX. When sending a model id to the TX it should always be in the range 0-63.

Now I get the normal 500Hz default for my models, which is what I would expect when not using Model Match. Thanks.

Great, thanks for reporting back.

I've merged the pending PR and the fixed id change so the Deviation master branch is the latest (and same as the latest test build). I put a "nightly build" in the Test Build section on deviationtx.com. Still working on the CI build changes.

Hi, I just built the recent firmware for my carbon fiber t8sg v2 and I was wondering if I still need to do the pin mod to get elrs to work. Thanks!

Yes, the mod is still needed. That can't be solved with just firmware..

I did the pin mod, trimmed the top pin and soldered it to the bottom pin, and I'm on your latest nightly but I'm not getting anything in my crsf menu. I flashed with uart_inverted disabled and opentx_sync disabled. My module is a hm es24tx (not the pro). What PPM in setting am I supposed to use in my model menu? Right now all of them give me no options in the crsf menu.

Opentx sync should be enabled. Don't know what happens if it's not.
ELRS master branch has a fix that eliminates some serial port errors, but 2.2 seems to still work.
PPM In should be None. The bidirectional serial port protocols like CRSF can't be used with PPM since they use the same serial port.

For some reason I had it in my head that I somehow had to enable the external module like in edge tx... It works great with ppm in set to none. I turned off openTX sync trying to get it to work, it worked with it off but I reflashed it with it enabled.

Thanks for everything!

Glad to hear you got it going. Thanks for posting.

Hi

I use BetaFPV ELRS Micro TX Module 1W Edition at Jumper t8sg v3 it works great.

But there are nothing in CRSF but "bit rate" when I use Jumper 2.4G ELRS TX Module AION NANO at DEVO 7E.
I use transmitter’s trainer port (tip connector) to connect this module and it can bind a receiver and work normally.

Is it normal for Devo 7E using a CRSF protocol (also ELRS) or something i have done wrong.

firmware : dba34f0
Thanks.