… so the script is also not executable. I take a full screen widget, select “Yaapu Telemetry” and when I click on configure, the configuration stops at the language again. Then you can also see the red exclamation mark at the top, which indicates the .lua error.
I cannot replicate your issue, I don’t have that radio so what I could do was delete all models in the simulator and start from scratch, create a new model with the wizard and setup the widget for that model and it runs without errors.
Which RF are you using?
From your error the widget is not initialized, did you try to replace the SD, could it be corrupted?
An external ELRS module.
The SD card is OK. I’ll ask on RCG again later if anyone can reproduce the error with another transmitter.
@Target0815 I read the create() handler issue on the ethos thread, try this version please
yaaputelemetry_x18.zip (53.2 KB)
Great … I’ll try it out tonight.
Thank you!
Unfortunately it does not work completely yet …
The configuration is now complete again (was previously cut off after the language selection). However, the widget is not displayed and the following errors are listed:
The files mentioned (utils.lua and frame_names.lua) are available, can be opened using Editior and have meaningful content. I can reproduce the behaviour on 2x X18SE, so no problems with transmitters or SD cards.
@Target0815 one more try 
yaaputelemetry_x18.zip (53.1 KB)
@yaapu doesn’t look much different:
Hi Alex, hi Reinhard,
(i’m the guy who opened the ethos-create-issue on git)
on your latest “1.5.18” optimized revision i changed the “libload” statement into rel. path adressing:
local lib = dofile(“./lib/”…name…“.lua”)
At least the widget starts on my X18 and i do have all the config parameters.
Reinhard, could you check please,
you know i’m a “yaapu script newbie”
i’ll try to contact Bertrand today because of the create handler issue
regards
udo
main.zip (13.2 KB)
this doesn’t make any sense, absolut paths are used all over the code. Must be something else. I also had a talk with Bertarnd about the create() stuff and no changes from his side there as well.
As a matter of fact I have my widget running on ethos 1.5.18 and elrs 3.51 on both my X10 and X20 radios so I guess it “should” work, seems very specific to the x18
It turns out it makes sense
X18 has both SD and NAND storage, and LUA script can be launched from both.
The running script “does not know” which HW storage is running from so by using rel paths it will go to the correct “root”.
thanks for helping me dig this out
1 Like
BTW explicit handling for multiple storage devices is something new in ethos 1.5.18, it’s a performance tuning side effect, this is why the issue popped up only now
Glad I could help, and it led to me getting my widgets up and running as well.
It was definitely not a problem with the create handler—just that the error messages led me down the wrong path.
The simplest solution would have been to remove the SD card, but this way, I also brought the widgets up to date
@reinhard, are you using sdcards on your x18 too ?
Yes Udo, but only for screenshots and backups.
I can’t believe it … SD card out and the Yaapu script is running … (with the last change from Alex).
where do you guys store the map tiles for the mapping feature?
The widget needs to know it in advance or else try all possible positions (very bad solution).
Or assume the map tiles will be on the SD card, which would make sense actually, but there are radios without an SD card so I guess only correct solution is asking in the config and set SD as default
In my case, the map tiles are stored on the NAND memory. However, I don’t tend to use the map tiles (I use maps online via Mission Planner).
If the storage location can be selected or deactivated in the configuration, it can be used flexibly.
Yes, this is the problem that has been discussed in the last few posts.
@yaapu:
don’t know if you got the info,
1.6 will support new path-prefixes:
- AUDIO:
- VOICEx:
- BITMAPS:
- SCRIPTS:
- SCREENSHOTS:
- LOGS:
yes, this solution came up while discussing the issue with Bertrand.
Looking for a workaround for current versions