Add lvgl bindphrase setting script

[CapnBry]

For ExpressLRS 4.1, a utility to set a bindphrase. Builds on #3

There is a history saved to "elrs-phrase.txt" that shows last 5 as buttons the user can click to set the bindphrase to that but holy smokes if after 3 hours I could not get it to work. There's no way to set a textEdit's value?! Deleting it and recreating it lets me update it, but then the button just doesn't do anything. No error. Nothing. 🤷 Whatever EDIT: I sort of hamfisted got it working

RX Binding Functions

If there is no RX connected and the user selects the "Receiver" target, the user is presented with instructions and a Bind button. If an RX is connected when receiver is selected, an "Unbind" button is added to allow them to disconnect it and allow it to bind to someone else. Image below.

Zip file for users who want to use this now

Includes this entire repo with Jurg's scripts as well, unzip to the root of your SD card

elrs-bind-v5.zip

[CapnBry]

People on seeing this feature seem to think that it should be able to send a bindphrase to an RX that isn't bound, but we can't because send data to it. If this is the case, I've added a bind shortcut button to allow a bind to happen. Also there is an "Unbind" button added if the user wants to put the RX into binding mode when if it is connected.

[CapnBry]

• Renamed to "ELRS Bind Manager". Please delete elrs-phrase.lua, elrs-phrase.luac, and rename your elrs-phrase.txt to elrs-bind.txt after updating with v2 zip in first post.
• Updated to scale properly with LCD size

[CapnBry]

The language server test is dead wrong and it can fuck right off. I will now fight to have this check removed from check process. 😠

[robschii]

not working with edgtx 2.12.2!

[CapnBry]

not working with edgtx 2.12.2!

Which is the only version of EdgeTX I've tested it with! Maybe you can provide some other information about your setup? Handset, ELRS version, ELRS module type? Note that this only works on ELRS 4.1.0-RC1 currently.

[Larryvoll]

JUst a lil FYI, The GX12 has a 128×64 monochrome OLED, not a color touchscreen. LVGL-based Lua scripts (buttons, sliders, text fields, the whole "bind v2" UI style) were built specifically for EdgeTX's color-screen radios — EdgeTX 2.11 added that LVGL API, but only for the color-LCD firmware build. On the monochrome/B&W build (which is what your GX12 runs, even at 2.12.1), the lvgl object is never populated at all — it's compiled out, not "an older version." The script can't tell the difference between "firmware too old" and "hardware doesn't have LVGL," so it throws the same generic "2.11+ required" message either way.
Bottom line: no firmware upgrade will get this specific script working on the GX12. It's a hardware limitation, not a version mismatch. Probably true for all mono screens?

[charlybrown1982]

JUst a lil FYI, The GX12 has a 128×64 monochrome OLED, not a color touchscreen. LVGL-based Lua scripts (buttons, sliders, text fields, the whole "bind v2" UI style) were built specifically for EdgeTX's color-screen radios — EdgeTX 2.11 added that LVGL API, but only for the color-LCD firmware build. On the monochrome/B&W build (which is what your GX12 runs, even at 2.12.1), the lvgl object is never populated at all — it's compiled out, not "an older version." The script can't tell the difference between "firmware too old" and "hardware doesn't have LVGL," so it throws the same generic "2.11+ required" message either way. Bottom line: no firmware upgrade will get this specific script working on the GX12. It's a hardware limitation, not a version mismatch. Probably true for all mono screens?

Yes, I found the same issue with the Radiomaster Pocket.

[Ivan125976]

Hello! When launching on a Radiomaster Boxer running EdgeTX 2.11.6, a message appears at the top: "LVGL (EdgeTX 2.11+) requir...". The rest of the message extends off the screen.

[CapnBry]

Updated

• Added X to delete items from the History list
• Added "Both" target to set both the RX and TX at the same time
• Moved script to folder instead of at the root, allows for a ui subfolder and then the ability to render a B&W ui, however crippled that will be
• elrs-bind.txt (the saved history) renamed to history.txt

Updating

If you already have this installed, you'll need to delete the elrs-bind.lua, elrs-bind.luac, and move elrs-bind.txt to elrs-bind/history.txt if you want to preserve your history. Otherwise just delete elrs-bind.txt to let the new location start a new history.

[CapnBry]

Hello! When launching on a Radiomaster Boxer running EdgeTX 2.11.6, a message appears at the top: "LVGL (EdgeTX 2.11+) requir...". The rest of the message extends off the screen.

Hello and thanks for reporting this, but this should be reported in #3 as that's the base that displays this message and this builds on it.

[wimalopaan]

In elrs-bind-v4.zip you included a somewhat different version of @jurgelenas script: there are additional

• Phrase Echo
• Bind Phrase

fields at the bottom (see attached image).

What is the purpose of these fields?
Is this intentional or an left-over from some tests?

[CapnBry]

@wimalopaan Uhhhh is that in the simulator? The simulator is all fake fields and the source is the same as jurg's.

I just merged his latest but I have never seen those fields and they should only appear if the handset model ends in "-simu"

[wimalopaan]

@wimalopaan Uhhhh is that in the simulator? The simulator is all fake fields and the source is the same as jurg's.

I just merged his latest but I have never seen those fields and they should only appear if the handset model ends in "-simu"

Sure that is simulator.

I think the purpose of these fields are just to test the lastest features of the script, i.e. editing STRING parameter and editing FLOAT parameter.

I was suprised to see these fields at a position were for a real tx-module no fields are displayed.

Maybe they aren't needed anymore, since string editing is part of the elrs-bind-script now and the fake float field could be moved to the faked receivers page.

[CapnBry]

I'm not sure I'm following you. You were surprised to see fields for testing all the data types in the simulator? It's for testing all the field types. Also, is present in the PR this is based on so that's why it is here too and will also be present in master when all this gets merged.