Stuck on "Downloading board info" with Crossfire

[kristjanbjarni]

When using Crossfire and EdgeTX the script gets completely stuck on "Downloading board info".

Hardware/Software used:

• Crossfire Micro TX v6.13
• Radiomaster TX16S running EdgeTX 2.7.1
• Betaflight TX Lua Scripts 1.6.0

[klutvott123]

Sounds like it's an issue with EdgeTX. Which BF version?
I haven't had any issues downloading board info with opentx, crossfire, tracer, 1.6.0 and 4.3.0

[kristjanbjarni]

BF version is 4.2.8.

I also tested on Jumper T16 running OpenTX 2.3.14 with same results so this doesn't seem to be EdgeTX exclusive.

I also did testing on some older nightly builds and found the same issue, but build v20211024.4306 seems to be one of the last versions to work, but I didn't test every version.

[klutvott123]

you need 4.2.11. There was a bug betaflight/betaflight#11059

[beautown87]

This same thing occurs for me. I'm running Edge 2.7, Betaflight 4.3 with a mamba F405 MK2 flight controller. Note this seems to occur for select FCs as I have a different mamba F405 DJI MK2 and the lua works with that.
@klutvott123 are you saying we need to roll back to 4.2.11 and the corresponding LUA if we want LUA functionality? Thanks

[kristjanbjarni]

OK that seems to be the issue. I updated to 4.2.11 and it fixes the issue. I didn't realise that this version and higher was required since there weren't any BF version requirements listed. It would probably be a good idea to state this requirement for the release since a lot of people will probably run into this.

[klutvott123]

@beautown87 Which rx systems are you using? Is it the same for all the flight controllers you've tried it with? If it's ELRS you will need at least 2.0.1 for it to work.
BF lua 1.6.0 is backwards compatible, but for BF version 4.2 you have to use the latest maintenance release which is 4.2.11. Best practice for the lua scripts is to use the latest stable release.

@kristjanbjarni Done https://github.com/betaflight/betaflight-tx-lua-scripts/releases/tag/1.6.0

[beautown87]

Hi @klutvott123 I'm using ELRS V2.3.0 and I have Betaflight 4.2.11 on my quad so that is probably the issue - thanks for the note above. I'm going to flash 4.3 on it and hopefully it will work with the new LUA.
Note, I was not comparing apples with apples in my first note as quad 1 has BF 4.2.11 with mamba F405 MK2 (LUA 1.6.0 does not work) and quad 2 has has BF 4.3 RC 3 with mamba F405 DJI MK2 (LUA 1.6.0 does work).

[beautown87]

Updating to 4.3 worked for anyone interested. Thanks for the advice @klutvott123

[LeftStep]

I updated to 4.3 and am still having the same issue with LUA script 1.6...
Using EdgeTX 2.7.1 on TX16S.
Tried BetaFPV Toothpick F4 20A AIO V3 and SkyStars RC F722 F7, both with BF 4.3.
Tx is XF micro and Rxs are XF Nano all with Firmware 6.17.
Also tried nightly v20220614.6589 with same result.

[Thomas72fpv]

Hello, same problem for me. I have BF 4.2.5 and the same message "downloading board info". After one hour, nothing happened...
Any idea ?

[kristjanbjarni]

Hello, same problem for me. I have BF 4.2.5 and the same message "downloading board info". After one hour, nothing happened... Any idea ?

As noted in the comments above you need to update BF to version 4.2.11 or higher since there was a bug fix that resolves this problem.

[DaniLecx]

I'm also having the same issue, I'm stuck with "Downloading board info".
Here's my setup:

• EdgeTX 2.7.1 on QX7
• Betaflight 4.3.1
• Betaflight TX Lua Scripts 1.6.0
• Express LRS 2.0.0

[haslinghuis]

@DaniLecx see comment above:

If it's ELRS you will need at least 2.0.1 for it to work.

[dlwlsns]

Having the same issue, script build and VTX table both complete the process but it get stuck on "Downloading board info".
Setup:

• EdgeTX 2.7.1 on Taranis X9D+
• Betaflight 4.3.1
• BF LUA Scripts 1.6.0
• Crossfire 6.17
• FC: HGLRC Zeus F722

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

[github-actions]

Issue closed automatically as inactive.

[klutvott123]

#447 should fix this