ExpressLRS LUA not opening with 2.12.0 RC1 for External Modules

[planemann2000]

Is there an existing issue for this problem?

• I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

ELRS lua not able to open with the firmware 2.12.0 rc1. Tried with two different transmitters ( Radiomaster TX mk2 and Eachine TX) with no success. Ranger Micro firmware v 4.0.0 rc2 external module used. Other lua's worked OK. backed up to 2.11.4 and everything was Ok (both transmitters)

Expected Behavior

ELRS lua should open.

Steps To Reproduce

Install firmware 2.12.0 rc1.
try to load Expresslrs lua
will not load

Version

2.12.0-RC

Transmitter

RadioMaster TX16S / TX16SMK2

Operating System (OS)

No response

OS Version

No response

Anything else?

No response

[pfeerick]

Can't reproduce on either TX16 w/ ELRS 3.5.6 or V16 w/ ELRS 4.0.0-rc3, both running EdgeTX v2.12.0-rc1, with internal modules. Can reproduce with external modules on both, with Ranger and Nomad modules.

[3djc]

I cannot reproduce.

TX16S, 2.12RC1, Nomad module, baudrate set at 921k (since I'm running at 500HZ)

[3djc]

Can reproduce at 5,25mbps, but seem to work fine at 3.75 here (both Nomad and Ranger)

[mha1]

The reason is most likey due to CRSF decoding errors with external modules at 5.25M. 921k works fine, the higher the baudrate the more CRSF decoding errors are present. This shows CRSF CRC and length decoding errors combined at 5,25M over a period of 2.5h:

[gismo2004]

This is the case quite some time now: https://discord.com/channels/839849772864503828/839856795781431317/1441695154611294341

#6816

[pfeerick]

@planemann2000

• Check the baud rate you are using in Model Settings -> External RF... it seems more likely to not respond at 400k (which used to always be fine)... 921k is consistently responsive.
• Double check you are using the latest ELRS Lua... I was running an older one which was "supposed" to still be fine according to the ELRS release notes but it also hung up once or twice - although that could just be coincidence.

I can still reproduce this reliably with the RM Nomad module, not so much with the Ranger, although the Ranger is running 3.6.x still, so it could either be a hardware and/or firmware version specific combination.