I activated on the original model but forgot to enable on the new. Now it works with new model.
Any idea why the new model works but not the original. I had encounter this issue before not sure why this is the case?
I’m not sure. From OpenTX 2.3.9 to EdgeTX 2.8.0 there’s been a couple of changes how models are stored. Maybe that was an issue.
Glad to hear it’s working now.
No idea. I would say the combination of Ardupilot, TBS stuff and Yaapu is not completely robust. When it all works it’s great but sometimes getting there is a challenge. At least that’s what I have found. EdgeTx V2.8 did fix some annoying things with running Lua scripts.
1 Like
That was going to be my next question. Thanks!
I can confirm that creating a new model from scratch fix my issue, but why Yaapu Debug is not running? I am seeing completely blank dark screen.
Crossfire Conf. Screen
Is the “Yaapu Debug CRSF.lua” file in the SCRIPTS>TOOLS folder of the radio Sd card?
For non CRSF users here’s another lesson I learned today:
When you upgrade to EdgeTX2.8 and Yaapu 2.0 you will also need to update your multi-protocol module. I updated a radio that had an older firmware on the multi-protocol module and there was no telemetry data on FrSky D16 drones. Once I updated the 4-in-1 module to 1.3.3.20 the telemetry worked again.
4 Likes
Aha. So that may be my issue.
1 Like
Indeed, the price you pay for bleeding edge is the pain associated with updates. I love ExpressLRS and am unlikely to use any other protocol anytime soon. But I’m keenly aware of the hassle required if/when I choose to update RC firmware.
1 Like
Problem solved! I did not realized that EdgeTx screen has scroll down has multiple Yaapu Debug lua scripts. I was pressing Yaapu Debug, when I should have scroll down to the Yaapu Debug CRSF.
Typical user error.
3 Likes
Excellent! I have struggled a bit with the combination of Ardupilot, EdgeTx, CRSF and Yaapu also but once it’s worked out it’s awesome! I
3 Likes
Anyone else notice this one:
When I switch models the Yaapu script seems to stall. I get the message that it’s “ready” but the screen gets stuck on “initializing”. The only way to clear the issue is if I power cycle the radio. Once it’s running however there doesn’t seem to be an issue. I’ve also tried to reset the flight and all the timers, but no luck.
I have upgraded from 2.6.0 to 2.8.0 edgetx and six of my sensor coming from passthrough freezes randomly
VFAS ARM GALT THR etc freeze down even with new 2.8.0 stable edge tx…i dont have this problem with 2.6 or 2.7
Previously reported issue
Setup:
Tx16s mk2 + TBS crossfire 6.19
Arduplane 4.4 dev /Matek fc f405 wing
Yaapu lua also installed 1.96 dev version with crsf enabled
Any idea?
Update to Yaapu 2.0 or later
https://github.com/yaapu/FrskyTelemetryScript/archive/master.zip
1 Like
Ok…thanks…thats my final chance …i will do 
Hi,
On my Radiomaster TX16S, I’m running 2.8 and have downloaded yaapu 2.0 but can’t get it to work (No telemetry)
The model has Pixhawk 2.4.8 (clone) on latest plane firmware.
I’m also using Siyi FM30 External module.
Is there a chance someone has it working with similar hardware as mine so I can get an idea what settings I should have to get it working please?
Im using yaapu script (2.0.0beta2 dev)with tx16s on Edge Tx 2.8.0. I ve experinced that the script sometines stuck in the initialization. I had to go into widget setup to start it loading.
FW arduplane 4.4 dev
Found this post about similar issue here: Yaapu telemetry repeat initialization
Yaapu stuck in initializing - YouTube
hi,
I’m using Radiomaster TX16s running EdgeTX 2.8.1 . I want to run yaapu telemetry scripts but when I try to do it , I get this. Some of the screen didn’t show any image at all. Can somebody help me with this?
I use FrskyTelemetryScript-dev.
Try this version: https://github.com/yaapu/FrskyTelemetryScript/archive/master.zip
What type of receiver are you using and how do you have it connected?