inavflight / opentx-telemetry-widget Goto Github PK

Describe the bug

RM TX16s - One day when using specific model on radio, started getting error of cpulimit
Changing to other models works fine

Appears a large number of logs associated with model cause this error

To reproduce

1. Set up any model
2. In my case I have SD card logging enabled via Special Function when arm condition met
3. Accumulate numerous logs (actual per model limitation not known, only that flushing log folder rectifies issue)
4. Next startup receive error, presumably one of the startup functions is to parse log files and crashes when too many for the model are in there
   4a. Able to work around as well by changing model name thus breaking link to SD card logs

Expected behavior

Clearly this is some technical limitation or similar, expectation is to have unlimited logging, however, I suppose some reasonable accommodation such as only look at last X number of logs to rectify problem.

Screenshots

N/A

Radio and model settings

Additional context

hello to all devs
I have a Horus 10s Accst with R9M reciver and modul
widget ver 2.2.0
drone with 722 chip with betaflight 4.2 all parts of the widget works but not the artificial horizon .
also have a strange behave on horizon that flips upside down when ever I connect the drone to power blue sky down brown earth up
on betalight configurator all is correct on 3d preview.
by the way older version which I had worked but I delete it and don't remember ver num.

Describe the bug

On a new install the SCRIPTS/TELEMETRY/INAV folder does not contain the "pics" folder or the fourteen .png files needed for various icons and backgrounds when using the iNav.lua script.

Also the "cfg" folder is missing from the SCRIPTS/TELEMETRY/INAV folder, which is needed to store configuration files for each model that uses specific configuration selections other than the default settings.
Without this folder the configuration *.dat file is not saved when exiting the configuration screen.

To reproduce

Remove the SCRIPTS/TELEMETRY/INAV folder and files.
Reinstall all files from version 2.0.0 release zip file.
Viewing Screen is now missing icons and backround colors.
Also any configuration changes made will reset to defaults when radio is restarted.

Tested on Jumper T16
EdgeTX current nightly

Describe your question

Hi, I love this script and the clever teamplay for inav and opentx. Unfortunatly I was pretty unsure, if my Radiomaster TX12 will be supported, as it's not listet, while other brands and models are explicitly listed. Thus I might decide to buy a more expensive modell or other brand, while this one working fine.

Expected behavior

EIther list all supported radios, or generalise description that all OpenTX radios will work? (not sure which one is better / easier)

I have a jumper t12 and t-lite (OpenTX 2.3.14). How do I get to the settings menu?

Describe the bug

the script works well, but there's no way to go in configuration menu. It seem like there'is no assigned button to do that.

Dear modeling friends, I ask you to help me get my lua inav to work on my taranis X9D 2019SE transmitter. As described, I downloaded the unzipped LuaTelemetry-Taranis-en.zip file, then I inserted the three files in the telemetry directory of the SD, then as recommended I did the new search for the sensors and reading its value next to each sensor. Then I ran the lua ivav and all the sensors and artificial horizon appeared on the transmitter display. pity that I do not read any sensor value marks everything to zero and the horizon does not move. I ask you the courtesy to tell me what mistake I might have made and why the installed lua does not work. Thanks so much for your time

When Mavlink protocol is used between Ardupilot and Crossfire TX, 'FM' (flight mode) don't show in sensors.
For this reason script doesn't detect CRSF and not work properly.

Solution:
change in 'other.lua' FM -> RFMD (RFMD - uplink, update rate - is always in sensors when used Crossfire TX)

data.fm_id = getTelemetryId("RFMD") > -1 and getTelemetryId("RFMD") or getTelemetryId("PV")

1. Be sure the OpenTX/JumperTX firmware on your transmitter includes the luac build option, video instructions linked here:
   Running Edgetx companion as root I'm able to load and flash tx16s-a55aff0.bin firmware to radio. It takes about 5s and I
   see a flashing done text. Sadly the radio boots in emergency mode. I was able to shut it off and restart but it
   loads some old firmware Oct 21 2010? I also flashed via OpenTX companion with similiar results.

I'm using Debian Linux. Trying to get the OpenTX Lua Telemetry script to execute from the /Scripts/Telemetry folder on sd card. EdgeTX 2.7.1 firmware on RadioMaster TX16S.
2) When installing Lua Telemetry, be sure to download the latest LuaTelemetry.zip linked here:
I did this.
https://github.com/iNavFlight/LuaTelemetry/wiki/Installation
I did this.
3) Another possible reason for this error is that you're trying to use other Lua scripts on the same model.
I'm not using any other LUA scripts on this model.

4. Too many unused models.
   I deleted a few but no change. I only have 13 models.

Thanks!

An Edge "enhancement" in 2.6-rc2 breaks backwards compatibility in getFieldInfo and hence the inav script.
trivial fix inbound ...

Describe your question

In the inav lua script the ability to play log files seems to be greyed out. Am I doing something wrong?

To reproduce

1. Go to the inav menu and scroll down and try to click on the playback log
2. The playback log is greyed out
3. Should it be doing this?

5. I think I have setup logging properly and will upload my logfile created from the radio below
   FPV Arrow-2022-05-14-125221.csv

If you're getting a not enough memory error, it means you're out of memory on your transmitter. The Taranis series has very little free memory to work with for Lua scripts, so this error is quite common. There's a few things that typically cause this error which are listed below:

1. When installing Lua Telemetry, be sure to download the latest LuaTelemetry.zip linked here:

https://github.com/iNavFlight/LuaTelemetry/releases/latest

Also, please see the following instructions for correct installation:

https://github.com/iNavFlight/LuaTelemetry/wiki/Installation

2. Another possible reason for this error is that you're trying to use other Lua scripts on the same model. While you can have multiple Lua scripts for the same model, there's not much memory to work with on the Taranis transmitters. For example, if you're trying to use the Betaflight Tx lua script as well as Lua Telemetry, you'll probably run out of memory. If VTx control is desired, try using the OSD menu which allows you to change VTx settings right on the OSD.

3. Too many unused models. Each model slot setup in your transmitter takes up valuable memory. Many times models are backed up to tweak settings without deleting the backups when finished. By deleting unused models, memory is freed that can be used for other things, like Lua scripts.

As this is a common issue that seems clear by the error message and covered in the Wiki, I would appreciate if you could let me know how the instructions could be improved to avoid any confusion.

Thanks!

Describe your question

To reproduce

1. Go to '....'
2. Click on '....'
3. Scroll down to '....'
4. Should it be doing this?

Expected behavior

Screenshots

Additional context

Any chance this LUA script can be made to run on FrSky's new line of radios running EthOS?

Hi, Can you pls add these 2 features:

1. in config make a choice if will be artificial horizon grey / solid black (Im using BW LCD on taranis and grey is not so good visible)

2. ILS (I mean that localiser is needed / glide slope si not needed / beacons optionaly if you wish)
   Example to solution
   airplane will be powered up to start gps locating and sending telemetry

place airplane to begin of runway
in config menu of lua telemetry select item "store begin of runway" (to store gps1)
place airplane to end of runway
in config menu select item "store end of runway" (to store gps2)

and fly

lua can calculate runway axis from gps1,gps2 and also
devaition runway axis to airplane gps position
on LCD will be visible as localiser or -+ deviation in meters

maybe it can be better explained from video
https://www.youtube.com/watch?v=Ra0XAPxuzdY

Thank YOU so much
WBR .s.

BTW. congratulation - this is very nice app. thanks

PS:

Glide slope is by me irrelevant due to defferent landing curve of any models according to weight of planes, trees on begin of runway and skill of airplane to loss some speed before fall. Special kind are JETs but as you wish (so i thing that only take memory without effect)

beacon can make sounds in case landing ( airplane have heading to runway -+ XX degrees and devaiation from axis is less then YY meters - better to have choice in config because both is affected by windy from side)
and how about beacons distance with different sounds ??? Also configurable ???

pls take the direction into account. You can define runway from left to right, but you can land from both sides.
it mean that localiser dont have problem, but heading for beacon signal can be little bit complicated.

I got it all setup but when i plug in my Dolphin lua script says "ERROR in background(): bad argument #1 to 'get value' (string expected, got nil)" What does this mean?
Error does not show of aircraft isn't connected

Tx16s

Widget chrashes TX16S into emergency mode on OpenTX 2.3.15

When switching to the widget screen on the TX16S updated to OTX 2.3.15, radio crashes.
Trying to add the widget in a new screen also ends up in a crash.

Radio and model settings

Radiomaster tx16s OpenTX 2.3.15

Describe the bug

I have a Flysky EL18 using Crossfire, can't get Lua Telemetry work on it

To reproduce

1. Go to 'Screen Settings'
2. Layout 'Full screen'
3. Click on 'Setup widgets'
4. Select widget choose 'iNav'
5. See 'ERROR in refresh(): bad argument # 1 to 'getValue' (string expected, git nil'

Expected behavior

Get a view of INAV Lua Telemetry

We have made some changes to the way that colors are handled in EdgeTX, and we have become aware that this causes an issue, if hard coded RGB565 color values are used instead of values returned by lcd.RGB(r,g,b).
The solution is to replace e.g.
color1 = 0x0AB1 by color1 = lcd.RGB(8,84,136).
I apologize for the inconvenience, and hope that you understand!

Tx16s on edgeTx 2.6 with Ghost module (race mode with telemetry).
Drone on betaflight 4.3-rc3
OpenTX-Telemetry-Widget on dev latest.

The INAV widget do not display the battery information properly.
The telemetry is working as the up-right corner display the correct voltage.

Thank you

To Developers:
I want to run Telemetry Lua on iFlight commando8（EdgeTX 2.8.0）

But I can't enter the "Configuration menu", even if I press the "menu" button on the remote control.
Other operations are OK.

How can I solve this problem？
Thanks.

Is your feature request related to a problem? Please describe

Today the way iNav radar is implemented using an TTGO (ESP32+LoRa) board is great but here is a list of issues that I see.

1. Relying on in-craft hardware that is not very cheap.
2. Adding another bit of RF equipment with a different frequency on the craft (not ideal for long range)
3. Though the visual clue about the position of your co-flyer is great but then it crowds up the OSD and with lag can be misleading. (needs significant delay tuning)

Describe the solution you'd like

The idea is to exchange telemetry data between the pilot radios using the serial ports on openTX / EdgeTX based radios. Next do a bearing calculation in the respective radio and 'speak out' the bearing in a 'Clock-bearing & Altitude' format.
More detailed steps (refer to the attached image):

1. Radio A receives full telemetry data from the craft. (already exists)
2. Radio A sends its data (GPS position, Altitude, ground course, speed, craft name) via a serial port (E.g. AUX1 on the TX16S) - requires the serial port to be configured as LUA in the radio settings -->hardware of EdgeTX??
3. Radio B receives the data (about craft A) via its serial port (e.g.AUX 1 on the TX16S) . While also sending out its own data packet on the same port.
4. Radio B runs the data from craft-A through a modified version of radar.lua (which already has heading calculations) in the scripts-set. sends the results as clock-bearing, altitude and speed callout in Audio.

For the new radios with bluetooth and headphone jacks built-in (like the TX16S mark2)... it will not require any additional hardware.

Typical use case scenario (imagined)

1. Pilot A /Pilot B (user-s) connect bluetooth modules and headphones to their radio's AUX1 and headphone jacks respectively.
2. Users configure the radio to let LUA access the AUX1 port. (radio settings --> serial port in EdgeTX)
3. There is already a screen configured with a full screen widget for the iNAV LUA script. User enters the config screen using stick positions.
4. <<we will need a method to setup the bluetooth connection between the radios... maybe there exists another LUA script to set up... mode/pin/name/pairing etc...for the bluetooth modules>>
5. Navigate to the 'WingMan' option on the list and change it to 'ON'. and set the audio callout volume on a switch... (maybe other preferences can be configured here)
6. They launch their crafts and if one user raises the volume slider all the way up, the radio speaks into the earphone "Keith, 2 O'clock 50meters away, Altitude 85 meters, 65 kilometers per hour" (Keith is the other craftname)
7. Once the user has sights of his 'wingman', he can flick the toggle switch to make the volume (only for this feature) zero (inaudible)... but the entire system keeps doing the calculations. of tracking each wingman!

Describe alternatives you've considered

• I have seen the iNav Radar with ESP32+LoRa being used. I think that is an overkill for what it achieves.
• I dont know well about BLE 4.0 and 5.0... maybe they allow mesh networks with multiple pilots?

Additional context

I have been running EdgeTX on TX16S with ELRS for control+telemetry so many of the assumptions and references are to the same setup. I have tried to be as generic as possible after studying a bit of the codes/features from all of these projects.

I could have dug down and coded the project myself. But I guess, with my coding skills it would take ages!... and there are others out there who can do it faster and more efficiently. I dont believe the effort is very high compared to the features/benefits. I am happy to help/discuss with anyone who plans to take this up.

Describe the bug

Tengo un TX Radiomaster TX16S, modúlo ELRS Beta FPV de 1 Watts y el LUA INAV se freeza.

To reproduce

1. Enciendo la radio
2. Enciendo el modelo con el RX
3. Toma toda la telemetría muy bien
4. A los 20 o 30 Segundos se freeza el LUA y no funciona más (incluso los audios), pero todos los mandos y el receptor funcionan bien.

Expected behavior

El comportamiento esperado es que funcione todo como enlos primeros 20 segundos.
¿QUE PUEDE ESTAS SUCEDIENDO?

Is your feature request related to a problem? Please describe

ELRS v3 introduced several new RF modes, leading to inaccurate RF mode display on widget top bar if using ELRS v3. As is, it works fine for those using ELRS v2, though.

Describe the solution you'd like

A new list should be added in funcs_h.lua file (in the title() function), which includes the 13 different RF modes from ELRS v3 for correct displaying. However, to keep backwards compatibility with ELRS v2, the current list (same file, line 64) should be kept. The script should then detect if the user is using ELRS v2 or v3 and choose the list accordingly.

Describe alternatives you've considered

If it was just a matter of expanding the current list, I'd gladly to do it myself and contribute, but the detection between ELRS v2 and v3 is above my Lua scripting skills...

Additional context

Reference for all RF modes implemented in v3:
https://www.expresslrs.org/3.0/info/signal-health/#rf-mode-indexes-rfmd

I am running V2.2.1 (had same problem with previous versions as well) on a Jumper T16 running EdgeTX 2.7.0 and a R9M TX module. The LUA widget is not showing any telemetry despite the fact it shows up fine in the model settings Telemetry page. Over a year ago I upgraded from OpenTX to EdgeTX and this is when it stopped working. I tried many things to get it working and then just gave up. I have three different fixed wing aircraft and they all have the same issue. I am currently running iNav v6 but had the same problem on previous versions (V4 and V2).

I guess my first question is whether this specific combination of T16, EdgeTX and a R9M should be working? Does anyone else have it working? If the answer is yes, I'm wondering what I might try to get this working? I am able to create a standard widget to display things like distance to home, altitude, GPS co-ordinates, flight battery voltage, etc. but would much prefer to use the LUA telemetry script. Thanks.

Screenshots

Here are some screenshots showing the telemetry working in the model setup and a regular widget and one showing it not working in the LUA script.
OneDrive_1_2023-08-12.zip

Radio and model settings

The EdgeTX models and .dat file are attached. The models that have this problem are called Dart 250g, Nano Talon and Nano Goblin.
LUA-Files.zip

Describe the bug

I have a Taranis X-Lite Pro and flashed EdgeTX "Flying Dutchman" v2.8.2 and Update the Telemetry Widget to the newest release Release 2.2.0
https://github.com/iNavFlight/OpenTX-Telemetry-Widget/releases/tag/v2.2.0
Bevor I had an old version 1.7.5 which was quite old but was running as Widget on EdgeTX "Flying Dutchman" v2.8.2

I get an Syntax Error:

Syntax error
?:0 attempt to index field 'table' (a nil value)

To reproduce

Update Widget from Version 1.7.5 to 2.2.0

After Startup of Radio:

1. Press "TELE" button

Expected behavior

No Error

Screenshots

Syntax error
?:0 attempt to index field 'table' (a nil value)

Radio and model settings

Taranis X-Lite Pro with FrSky R9M Lite Pro Modul 900mhz

Chimera7_dat.zip
document1.zip

How to enter the settings page on iFlight Commando 8?

Long press of the menu button seems to have no response.

Use Telemetry Lua V2.2.1 and EdgeTX 2.8.0.

Hi Guys I need a support, I have installed the latest version of Inav lua on my Taranis X9D SE 2019 transmitter. Everything seems to work fine, I ask why when I change flight mode from Acro to Manual no voice reminds me that I have switched from a mode to the other, how can I enable this function that I find convenient? Thanks in advance for your contribution.
Franco

Describe your question

To reproduce

1. Go to '....'
2. Click on '....'
3. Scroll down to '....'
4. Should it be doing this?

Expected behavior

Screenshots

Additional context

Describe the bug

Hi , I am having a problem, every time I arm the motor I get a critical battery alarm, with a Full Battery, alarm stops when motor disarmed.
However, I do get a GPS lock, Ok to fly and the motor will spin.
I have reset the flight and the telemetry, individually and together, prior to powering up the model and with model powered on.
The TX16s INAV LUA telemetry screen displays current Battery and Fuel at 100%, but I see it flashing yellow /red,
Also, in the actual TX16s telemetry sensor screen I see the voltage fluctuating between 0-99%.

I have followed the instructions in the WIKI R/T battery information and have matched the in INAV settings in configurator and the INAV lua on the TX16s I am using Crossfire, so I did not do the CLI changes as stated in the battery information. I did not have this problem until I tried changing over to EdgeTx then I changed back, after several failed attempts, everything else seems to working with the TX16s and the other models not associated with INAV.

Model #1
Ranger-FPV2022

Radiomaster Tx16s Running 2.3.15-otx
Crossfire nano RX
INAV config. 4.1.0
Matek 765 running INAV 4.1.0
2 x 5000mah 3 cell Lipo's

Thank You very much.
I hope it is something simple that I have missed!
Cheers

RangerFPV2022.zip

On a Taranis X9D the function of the (+) and (-) buttons is inverted. (+) which is physically the upper button goes down the list and (-) which is the lower button moves up. Same behaviour on the OTX simulator.

Describe the bug

OpenTX version: 2.3.11
Transmitter model: Radiomaster TX12
Telemetry protocol: FrSky S.Port
RX&TX: QCZEK LRS

I am unable to enter INAV Lua configuration settings on Radiomaster TX12. It is working fine on Frsky Q X7 with the same QCZEK LRS RX&TX. Looks like the problem is that the script is not recognizing TX12 hardware buttons.

To reproduce

1. Press the TELE button to start the widget
2. Try short and long pressing all buttons and the jog dial to enter configuration
3. Try throttle max, yaw right as suggested for Horus radio
4. No luck

Expected behavior

Enter the script configuration settings menu by pressing one of the buttons (perhaps PAGE?)

Additional context

I have checked the docs, but found no answer: https://luatelemetry.readthedocs.io/en/latest/Configuration-Settings/

Greetings,

I've been trying to configure the alarms (I use Li-Ion and the alarms are set too high) and It's not possible to enter the configuration with a Jumper T-Lite with EdgeTX.

In the guide is stated that you should long press the "MENU" button to enter, but none of the buttons on the radio get me into the configuration menu of the LUA.

Can this issue be solved or can I configure the alarms in the LUA any other way?

Thanks.

Is your feature request related to a problem? Please describe

The widget doesn't seem to like ELRS 2.4 @ 50 Hz (even with 1:2 TLM). The widget will only load a few values and in general not work as expected. Switching to 100 Hz full addresses the problem. Have tried lowering the TLM_REPORT_INTERVAL_MS to 10 ms without success.

Describe the solution you'd like

The widget to work as expected with 50 Hz mode.

Describe alternatives you've considered

Have tried choosing the highest telemetry rate (1:2) which should provide enough data. For example, if I choose 100 Hz full with 1:32 ratio, this is much less data but the widget seems to work as expected.

Additional context

N/A

This is a placeholder (as well as statement of fact) to reference the upstream edgetx issue EdgeTX/edgetx#823 which is quite noticeable with the inav widget.

As noted upstream, the using the page buttons is much faster.

Describe the bug

On CRSF the transmit power indicator stopped working.
I am on CRFS FW 6.17 and OpenTX 2.3.15 on my TX16s

To reproduce

• Create new model
• Discover Telemetry sensors
• Run the Telemetry Widget

Expected behavior

Usually the widget is showing the transmit power of the CRSF module.
I have another, older model on my radio (didn't refreshed sensor discovery on that) - there the mw Value is showing up normally - same FW and hardware.

Screenshots

old model - no new sensor discovery

new model - with new sensor discovery. I also noted the name TPW2 is different - on the old model it is TPWR.

I have never been able to get this version to work on my Horus X10S Express, with the latest official OpenTX firmware.
As soon as I select the widget the tx goes into emergency mode.
While this version works, and I can't figure out if yours is a newer version than that.: https://github.com/teckel12/LuaTelemetry/releases/tag/v1.7.5

Describe the bug

I have a Taranis X-Lite Pro and flashed EdgeTX "Flying Dutchman" v2.8.2 and Update the Telemetry Widget to the newest release Release 2.2.0
https://github.com/iNavFlight/OpenTX-Telemetry-Widget/releases/tag/v2.2.0
Bevor I had an old version 1.7.5 which was quite old but was running as Widget on EdgeTX "Flying Dutchman" v2.8.2

I also have Expresslrs the current version 3.2.1, I switched this today from frsky, bevor the script works perfekt

To reproduce

switch from frsky to express lrs.
On call of lua widget:

Syntax error
?:0
attempt to call a field 'getElrsRFM' (a nil value)

Expected behavior

no error

Screenshots

Radio and model settings

Taranis X-Lite Pro with Radiomaster Ranger Nano Modul + RP3 Radiomaster reciver (also happens with RP1/RP2)

Is it support Jumper T-Pro?

hello to all devs
Describe the bug
Battery level display error on my TBS MAMBO and X9D 2019 (OpenTX 2.3.14)

Whether the problem is the flight controller?

To reproduce
The radio power on before the drone
Running the script
Percentage of battery is 0%
Battery voltage error

When The radio power on after the drone.The problem will be solved

Screenshots

Hi,

Can we please have a larger battery capacity option such as 20000mah?

If you're getting a not enough memory error, it means you're out of memory on your transmitter. The Taranis series has very little free memory to work with for Lua scripts, so this error is quite common. There's a few things that typically cause this error which are listed below:

1. When installing Lua Telemetry, be sure to download the latest LuaTelemetry.zip linked here:

https://github.com/iNavFlight/LuaTelemetry/releases/latest

Also, please see the following instructions for correct installation:

https://github.com/iNavFlight/LuaTelemetry/wiki/Installation

2. Another possible reason for this error is that you're trying to use other Lua scripts on the same model. While you can have multiple Lua scripts for the same model, there's not much memory to work with on the Taranis transmitters. For example, if you're trying to use the Betaflight Tx lua script as well as Lua Telemetry, you'll probably run out of memory. If VTx control is desired, try using the OSD menu which allows you to change VTx settings right on the OSD.

3. Too many unused models. Each model slot setup in your transmitter takes up valuable memory. Many times models are backed up to tweak settings without deleting the backups when finished. By deleting unused models, memory is freed that can be used for other things, like Lua scripts.

As this is a common issue that seems clear by the error message and covered in the Wiki, I would appreciate if you could let me know how the instructions could be improved to avoid any confusion.

Thanks!

Radiomaster tx16s edge tx version 2.8 latest version
Fr sky x8r with s port telemetry
Inav 5.1 on matek f411wte
Inav lua script 2.2 latest version
Unable to access widget configurator. stick movements don't work on mode 1 (throttle right) is there another way to access the configuration?
Voltage not displayed, unable to see vbat sensor. Other sensors detected no problem.
Same problem with 2 builds using the same hardware.
Results in constant low battery warning which I have no access to configuration to turn off. Re setting telemetry no use.
Be grateful for any help.

Radiomaster TX16S Expresslrs 3.2 and Edgetx version 2.8, mode 1
Radiomaster EP3 Expresslrs 3.2
Inav 3.0.2 on Matek F722 WPX
Inav lua script 2.2

I'm configuring a F5J sailplane where I mapped throttle on the right slider and flaps on the throttle stick. Flaps zero is stick full up. Now I'm getting a throttle warning in iNav lua while flight status is 'not ok'. As soon as a GPS fix is available and the status changes to 'ready', the warning is gone. So it's not really a problem, but rather somewhat annoying.

It seems to me that to generate the warning, always the throttle stick position is read regardless of the channel mapping. Is there any fix for this?

Is your feature request related to a problem? Please describe

In some cases, it's interesting to also track RSSI because even with a LQ near 100%, if the RSSI is dropping quickly, it means LQ could also start dropping soon. By tracking RSSI, you can have kind of an "early warning" of when LQ will drop.

Describe the solution you'd like

The user should have the option to choose between the current solution, where a bar chart with just the LQ% is shown and another option, with a simple text showing RSSI and LQ separated by a slash, as in "RRRdb/LLL%" (where R are the RSSI digits and L the LQ digits). For cases when the RSSI data for two antennas is reported via the telemetry, if the screen space allows, it could be "RRRdb1/RRRdb2/LLL%", where db1 and db2 are the RSSI values for antenna 1 and antenna 2, respectively.

Describe alternatives you've considered

Such a feature would only make sense for radio link systems that provide this detailed data. From what I have seen both TBS Crossfire and ELRS systems do, and they both use the CRSF protocol for data packets. So this extra display option could be enabled only for these systems.

Additional context

A more detailed explanation on RSSI and LQ and their meaning:
https://www.expresslrs.org/3.0/info/signal-health/

Describe the bug

The script was worked perfectly with my old rx-tx module (QCZEK LRS) but i bought a new Betafpv 868 elrs system. I am getting the necessary telemtry datas, but an another ID with the Qczek. So the Ianv lua didnt see the datas, only the Voltage and current. But all of the datas is availabke on the telemtry settings screen.

To reproduce

Expected behavior

The script has to see all of the datas and working correkt. Because elrs is using crsf if iam correct. And crsf is supported.

Screenshots

Radio and model settings

Additional context

All Fw is the newest. INav 6.1, OpenTX 2.3.15, iNav lua 2.2.1.

Describe the bug

I can open the options menu (left stick top right), I can select the option or exit the menu (right stick left / right). What doesn't seem to work is the scrolling up / down (right stick up/down) which means I can't select other options or change the current option in the menu

To reproduce

Open the menu and attempt to move up and down through the menu on the NV14 running edgeTX

Expected behavior

It should be possible to scroll up and down through the menu

Radio and model settings

Radio: NV14
OS: Edge TX 2.6.0 RC1
Crossfire
Luascript 2.0.1

Hi folks!

Describe the bug

I'm seeing a syntax error when attempting to run the widget (both the latest release and master):

Syntax error
?:0
attempt to index field '
table' (a nil value)

This happens regardless of whether a model is connected or not.

My guess is that it's actually a memory-related issue, but I'm logging it here in case other folks also run across it.

My setup:

• RadioMaster Boxer (ELRS version)
• ExpressLRS 3.2.0
  • Packet rate: 100Hz Full
  • Telem ratio: 1:2
  • Switch mode: 12ch mixed
  • Model match: off
  • TX power: 1000mW Dyn
• No other lua scripts running
• Only a single model, named "INAV"

To reproduce

(with the INAV widget configured as a telemetry screen)

1. Press "TELE" button

Expected behavior

I should see the telemetry widget.

Radio and model settings

This zip file contains only the etx file as the cfg directory is empty on my radio.

boxer.zip

Jumper T12 edgetx 2.5.0, оpenTX 2.3.14
Jumper T-lite openTX 2.3.14 (Haven't checked edgetx yet )
LuaTelemetry_v2.0.2-rc2
Mixed buttons up and down in the menu inav telemetry. How to fix?

When using EdgeTx using the elevator causes the widget to display min/max values. It would be nice if this did not happen on EdgeTx.

Thank you