yaapu
'pop frame' not callible on Ethos 1.6
I just updated my ethos fw to 1.6 on my Frsky Tandem X20S. Now I notice an error/warning icon on the top portion of the screen. It seems there is an error encountered calling this pop-frame?
Telemetry sensor works though and can still fetch the data from my flight controller. Any fix on this? I'm using ELRS module installed on the back of the X20S. The telemetry source to External Module (I didn't change it as this was working before). Telemetry sensors also indicate External Module as source
It only shows this screen, the script does not load unlike on the previous ethos fw
I tried updating the yaapu script to 1.3 and it still shows the same error.
I also tried another setup, where it uses mav2pt, and internal module as telemetry source. It worked just fine. I still get that popframe not callible error but at least the yaapu script works.. I guess the yaapu script only got issues with external module? What does this popframe do with telemetry from external module? It does not seem to affect the functionality of yaapu when using internal module though
rolled back to ETHOS 1.5.19 for the mean time, hope there will be a fix on yaapu soon!
I also filed this in the Ethos github. Their reply was "In 1.6.2 telemetry frames are popped with new method (sensor)." I am filing a request for them to version control their lua API library.
Hi, could you please test this version? yaapu_widget_1.4.2_ethos_1.6.x.zip
I have just tested this with the latest Ethos 1.62 and it works now! :-) Thanks for your hard work @yaapu Tried both on native Frsky telemetry (using Frsky Archer) and CRSF telemetry from my ELRS setup, both works great
Thanks for continuing to support Ethos, Alex. I also tried internal and external RF and had no issues. There are no audio files if doing a clean install, but an overwrite install worked fine.
Thanks for continuing to support Ethos, Alex. I also tried internal and external RF and had no issues. There are no audio files if doing a clean install, but an overwrite install worked fine.
The ethos team is giving me a hard time, pretty much they break the api at every major release, a real pain to support
Yes, agreed. I tried to advocate for some version control for the Lua API library, but it doesn't seem to be practical since they would need to keep multiple versions on the radio. I'm sure there is more they can do such as making new parameters non-required or creating a new API name if they refactor it entirely.
that's fully understandable @yaapu . I just hope ETHOS wont break it again.
@mikedkelly so for clean install, it isnt possible now, i guess this is just the patch :)
that's fully understandable @yaapu . I just hope ETHOS wont break it again. @mikedkelly so for clean install, it isnt possible now, i guess this is just the patch :)
I updated the github repo, clean install as usual is now possible
love you :) just for the sake of conversation, is this a frsky breaking things, or is this a new thing for new versions of lua in general? and also, is there some sort of donate now support me link? really love your work :) p.s. found the link :)
love you :) just for the sake of conversation, is this a frsky breaking things, or is this a new thing for new versions of lua in general? and also, is there some sort of donate now support me link? really love your work :) p.s. found the link :)
@sardelich thanks a lot for your support!
hm. it is still not behaving...it might be that I am missing some setup steps, but refresh is not very working, and I get some error now and then :/
that's fully understandable @yaapu . I just hope ETHOS wont break it again. @mikedkelly so for clean install, it isnt possible now, i guess this is just the patch :)
I updated the github repo, clean install as usual is now possible
Thank you again @yaapu :-)
hm. it is still not behaving...it might be that I am missing some setup steps, but refresh is not very working, and I get some error now and then :/
flash to latest ETHOS (make sure to make a backup of your models), put the yaapu files in the sd card (Both the common and those folders specific for your radio (800x400 for the x20s), overwrite the files. restart the radio and it should work fine. Oh, make sure to configure the yaapu widget settings as needed (enable CRSF support for ELRS and external module for the telem source, otherwise internal)
yep.did all that. I will get some screenshots soon. Im fighting with some escs now.....
as you can see there is some errors, and also FC is now getting 12.07V, that is reported in mission planner. ethos sees all the sensors when in discovery on telemetry on ethos.after maybe a minute or two it will update voltage readings, like the refresh is slooooow. I am running elrs full 333 on 2.4 only, with standard telemetry rate, backpack is at 921k baudrate, gemini nomad, if it helps
it takes roughly 1 minute to update the voltage on the display of yaapu screen. on standard ethos telemetry screen, the voltage will update, gradually dropping in maybe 15 seconds
Hi @sardelich, from the screenshot you posted you seem to have elrs version 1.0, it's old and does not support ardupilot, you need version 2.x. https://github.com/yaapu/FrskyTelemetryScript/wiki/Passthrough-over-CRSF-and-ExpressLRS After upgrading elrs you have to set a high telemetry rate, if you are on 333Hz @ 2.4Ghz use a 1:4 ratio, you can try 1:8 but not slower than that. Remenber to enable ardupilot's custom CRSF telemetry with RC_OPTIONS += 256 (set bit 8)
will do. just this elrs ver 1 and ver 2 is a bit confusing to me. is this a elrs firmware or protocol version inside the ardupilot? i am at [email protected], 1:1 telemetry rate, on a bench, rate is around 70-150Hz as reported in mission planner, sometimes it jumps over 300.i need to check rc_options (if this bit is enable passthru for crsf telemetry, it is enabled) ardu is latest stable 4.5.7
Set it up according to the documentation
https://github.com/yaapu/FrskyTelemetryScript/wiki/Passthrough-over-CRSF-and-ExpressLRS
hm. seems that changing telemetry rate to 1:2 1:4 or 1:8 even, works like a charm. updates instantly. thanx. however there is still this error:
?:-1: attemtp to index a nil value both receiver and transmitter are on elrs 3.5.3 everything else seems to work perfectly :) thank you :)
hm. seems that changing telemetry rate to 1:2 1:4 or 1:8 even, works like a charm. updates instantly. thanx. however there is still this error:
?:-1: attemtp to index a nil value both receiver and transmitter are on elrs 3.5.3 everything else seems to work perfectly :) thank you :)
attempt to index nil? when does it occur?
I believe I have seen that error before as well, looks like file path issues, as you can see here. Clicking on reset though somewhat bypasses it
yes, this means that the widget initialization code tryes a reset before the widget is fully initialized, once initialized it just works