I’m currently working on a drone setup using Holybro 5x, TBS Nano Diversity receiver, TBS CROSSFIRE micro TX V2, and running ArduCopter V4.4.3 firmware with Edgetx Providence on a TX16S remote.
I’ve encountered an issue while trying to use the Yaapu Lua script for telemetry. Although I’m receiving telemetry data on the TX16S, but the Yaapu screen displays a “No Telemetry Data” message.
It seems to be an issue in the Script.
I have the same issue on a recently set-up Radiomaster TX12 Mk2 with EdgeTX 2.9 and ExpressLRS.
I have telemetry in the Radio but the Lua Script does not recognize it.
BTW: The Ardupilot documentation is outdated. ExpressLRS works perfectly for Telemetry.
Nothing is missing in the install package and you don’t have to edit any .cfg files …
The installation is described here. You only need to go as far as the display configuration and select the “yaapu7” script there.
Then restart the transmitter and call up the Yaapu script with the TELE button. There you will probably see “no telemetry”. Then press RTN and TELE again and you are in the settings. Set “enable CRSF” to Yes at the bottom.
Then press TELE a little longer and RTN very briefly and you are back in the telemetry screen. Telemetry data should now be displayed when the connection is active.
If this is not yet the case, you must set the option “Use passthrough for CRSF telemetry” in the FC under RC_OPTIONS:
OK, that did the trick. Thank you.
I was not aware of this button combo.
After a couple of reboot action, the script actually does show telemetry but it comes with some bad side effect.
Apparently it changes something in the RF link and the FC looses RC thus switching to Failsafe in a 10-15s loop. It seems to “ask” FC for stuff like the ARM state and this switching around is fatal.
I run a BetaFPV 868Mhz TX module for long range 100Hz, telemetry rate Std 1/32.
Guess I’ll go back to the previous setup.
Thanks again. I hope this was also the answer the original author was looking for.
Hi!
I found your post as I’m having a similar issue to the person you were helping. Only when I try to use the TELE and RTN buttons as you described, nothing happens. Do you have any idea what I could be doing wrong?
I’m using a Radiomaster TX12 Mk2 for this attempt with the latest EdgeTX version as well as latest ELRS version on TX and RX. ETX is 10.4, I believe, with ELRS 3.4.3.
I do have a working yaapu setup with a TX16s from about a year ago or so that works with this same aircraft/RX tested today. It appears to be the same version of yaapu, so I’m thinking I’ve messed up my TX12 radio setup somewhere, but after trying it a couple times I’m not sure where. Maybe I should try an earlier version of yaapu?
I think this is maybe the part that I’m really getting tripped up on and can’t find any documentation for it either. I know that I didn’t do this when I installed the script on the ETX TX16s. Anyone have any ideas on if this is necessary or how to do it? Speaking specifically about the SRC -folder compilation instructions in the readme.
Also, I rolled back to ETX 2.9 as that’s the version the TX16s is currently on and I reinstalled the yaapu script to the corresponding folders (thought I didn’t do anything with the SRC folder). I set things up on the TX and now every time I start the yaapu script from the main TX page with the TELE button, I get a settings page for the script before it loads the HUD, etc. I can “enable CRSF” on this page and then advance to the HUD page, but I’m still not getting any telemetry on the HUD page itself for some reason, even though ETX can see 30 or so sensors in the Sensors menu page. Feeling lost here, I’ll probably try going back to the latest ETX and see if I can get the same results. I realized that the first time I installed it, I was using the “master” zip file from yaapu’s github - this time I used the latest B&W radio specific version. It seems that the file structure in both of them was the same, but I’m probably just missing something.
Okay, I have two TX12s that I’ve been trying this on, and after I got one to work, I tried the same process with the other and it seems to be reproducible - I also tried this on a Radiomaster Pocket with a fresh install of the script and it worked. The TX16s yaapu still works fine with yaapu after update to ETX 10.4.
My steps -
-Transmitter upgrade/downgrade to ETX 2.9 (because this was the ETX version that was working on the TX16s I had originally)
-Install yaapu from here following readmes but doing nothing with the SRC folder I screenshotted in my last post
-I am able to access the menu to “enable CRSF”. in the yaapu script by using the TELE and RTN buttons. I turn CRSF support “on”.
-Upgrade to ETX 10.4
-No change in yappu installed files or ETX SD Card
-Power up TX
-yappu works
This was done with the same aircraft the entire time on the same Ardupilot version/settings, same ELRS 3.4.3 version. Nothing changed on the aircraft side.
I don’t understand why this works, and I hope I’m just missing a step, but since the yappu script hasn’t been updated for close to 18 months now, I’m wondering if there is something that’s changed on the ETX side or something similar.
In short, the main problem I think this solved was that the “enable CRSF” menu option can’t be found when on ETX 10.4, which prevents the yaapu script from working with ELRS. Once turned on in a earlier version of ETX, this setting then seems to stay on even after a ETX upgrade, which I assume has something to do with the yaapu config file, as I didn’t erase/change those between ETX updates.
If anyone can shed any light on this or point out what I missed, I would appreciate it. If not, hopefully this can be helpful to others to follow the process. It seems that those who got it working earlier in this thread may have been on ETX 2.9.x version as they were posting right around when ETX 2.10 was being released. Maybe this issue I had has something to do with ETX 2.10…
It’s been a while since I got Yaapu working on a TX12. My college recently got it going but I know there was a challenge with it. I’ll see if he’s got any ideas.