Waiting for API versión

[xXadri107Xx]

I have just updated my taranis X9D PLUS SE 2019 to the last version of EdgeTX 2.11.4 without any problem. It is all working perfectly except this script, I tried all versions from the 1.4.1 to the 1.7.0 and the result is the same except in the 1.4.1 version that shows the pages but is not working.
The telemetry works perfectly in its page. The RX I am using is the FrSky Archer plus RS mini in ACCESS mode and updated to the latest version. In the betaflight I check all the config I see in different sites but any result.

I know probably with a newer TX will be the problem solved but I like this one and is the only thing that is not working correctly :(

Hope someone could help me although I know this radio is no longer supported.

[pfeerick]

What version of Betaflight are you running on the ... quad/drone? If it's a very recent, you might want to try a nightly firmware, rather than the quite old 1.7.0 release ;) i.e. from here https://github.com/betaflight/betaflight-tx-lua-scripts-nightlies/releases

[xXadri107Xx]

Thanks for your answer, Im running the latest version, 4.5.3. I also tried the nightly firmware but it still the same message. What is the difference between the normal releases and the nightly ones?

I'm willing to try anything you tell me.

[pfeerick]

Ok, 4.5.x should work with the 1.7.0 firmware IIRC, nightly Lua is simply newer builds from the master branch before they do another release.

Ok, so you're using FRSky ACCESS receiver in SBUS mode? SBUS only gives you the control link, no telemetry from the flight controller. For that, you need to look into either SBUS + SmartPort (control link on one wire, telemetry on another) or FPort (does both on one wire) - https://www.betaflight.com/docs/wiki/guides/current/FrSky-FPort-Protocol and https://oscarliang.com/setup-frsky-fport/ should get you started.

There is also an older video from JB that might help a little... configurator has changed a bit - i.e. receiver configuration is on the receiver page now - and for your receiver, you should be able to configure it between SPort/FPort/FBUS modes via the model setup page internal rf options... but it might still be of interest. https://www.youtube.com/watch?v=ZyKgBS9wmuc

[xXadri107Xx]

No, Im not using F. Port. I'm using S. Port. I have connected SBUS to SBUS pad and S.port wire to T2 pad. Of course both +5V and GND to each pad.

The only doubt I have now is if I need to activate the s. Port option in uart2 telemetry output page. I tried it but when saving it deletes every configuration in that page.

[haslinghuis]

Need to flash with the right options

[xXadri107Xx]

I also read that in other pages and although that was made in the first update I reupdate checking that, having the same problem.
Thanks for the help

[xXadri107Xx]

Hi again, I was just checking all the manuals and I see in the FC manual that S. Port cant be used in my FC. But there is another method to make it work. I leave here some useful information if someone have the same problem.

https://share.google/kBcZwiEhyfUCj3CqG

I will rewire the S. Port and I will update this issue with the results. Thanks for trying to solve my issue.

[xXadri107Xx]

Hi everyone,
I just rewired and configured as is said in the speedybee manual but it remains the same problem.
I read in other issues related to crossfire (is not my case but it could be related) that the problem was the baudrate but I don't have clear where to change that baudrate.. In the radio, in betaflight, in receiver...?