An Open Source Frsky Telemetry Script for the Horus X10,X12 and Taranis X9D,X9E and QX7 radios

Hi!
Regarding new “plot telemetry” screen on color displays (Jumper T16 in my case).
I can setup sonar or rangefinder. Both have the same readings but first is scaled in cm and second in meters. Is there any reason for having both? Personally I like sonar centimeters more, because there is no decimal part for meters so the displayed reading below 1meter for rangefinder is 0.

Regards,
Jacek

Hi, I was experimenting with different units, actually cm would work for both, but they really are the same value, it’s just the label that changes

btw, is it working for you? My test setup does work fine but I had reports from a user that cm sonar rendering had issues that I can’t replicate

Hi, sonar cm works just fine. I am using Benewake TFminiPlus via serial.

Is there any news about use yaapu script with Express lrs and ardupilot? It use the same serial protocol 23 as in case f.port receivers. Only difference the serial option in case of f4 fc s.

Hi check here current status Passthrough telemetry over CRSF (crossfire)

Hi. Alex!
Sorry to write here but i cannot post in the crsf thread currently and probably the issue its not only elrs or crsf specific.
So overall the 1.9.5 script working well on my X9D+ with matekf405( with ardu 4.1 and 4.2) and R9M modul
flashed with express lrs, but instead of rssi db or LQ I see only R:100/5 or R:100/3 on the top bar depending on what refresh rate i select for the module 200hz/100Hz.
I think this is the RFMD value but “100” does not changes even if my LQ drops below 90 or RSSI to -100Db or lower.
Is there any setup option to see Rssi or LQ on the top bar instead of RFMD? Or it will be fixed in a next release for x9d.
If my post is offtopic here i will delete it and move to crsf passthrough if i ll be able to post there again.
Many thanks

Hi,
you’re going down an experimental road here :slight_smile:
ELRS is reporting RSSI to OpenTX as negative values whereas CRSF reports them as positive so my script is going crazy :slight_smile:

Yeah i think so…OK clear… i ll be patient…hope it will be fixed soon :wink:
Thanks for reply here and your great work invest in this script!

I experinced something interesting…if disable crsf in yaapu menu…the RFMD value changes to RLQ data in a format R:99 and start workin as LQ


…the script works continously without issue (of course not power cycle the radio…as in that case i lost all tlm for yaapu)

Hello Alex,

I have been using luagcs with Fport of Frsky R9slim+. it was all good. and recently I started using Siyi Moduler with its FR receiver(yaapu script is running). the radio always shows on loading page(luagcs). can you tell me does siyi not supported or something I set incorrectly? thank you very much :grinning:

You don’t have to ask me :slight_smile:
Siyi is not Frsky, I think they implemented the MAvToPT protocol, so no bidir telemetry working,

thank you for your answers.

I did not know this part of information. I thought siyi is working with mavlink2 upload and download by the moduler bluetooth. so I guess it should work for luagcs…it is very good to know that it is not suported instead of trying to figure out what setting I was missing. thank you again. :grinning:

@yaapu, we ran into some issues using some of the latest components including an Archer RS. I see your comment from last month.

I’m guessing that’s not good for us, but we also tried with a R-XSR running the latest FrSky firmware. In that case, we kept losing and regaining all sensors about ever 3 seconds repeating forever. Any ideas?

Hardware/Firmware
FrSky Taranis X9-Lite ISRM 1.1.0/2.1.6FCC OpenTX 2.3.12-frsky
R-XSR 1.1.0/2.1.7 (Cycling working)
Archer-X 1.2.0/2.1.8 (No telemetry working at all, can only get RC)
CubeOrange, standard carrier board, 4.1.0 Beta 7, Telem2 port

Hello

I need some help. In the past I was using the sport convertor to get the tx/rx connected to the sport of frsky x4r-sb. I learned that you can get uninverted sport connection to the receiver

  1. How does the cable setup look like if i get the uninverted sport signal from the receiver how it is described by OscarLiang. Do I have to drill both rx/tx cables from pixhawk and connect it to the uninverted signal pad of the receiver like with pixracer?
  2. What serial parameter has to be set in the pixhawk for that setup.

Thanks very much for any support

Harald

Hi all,

but at present, with these modules, does the script work?
I need a summary :slight_smile:

Hi Alberto, ELRS support is experimental, it kind of works by using high telemetry rates, check here for more info

it’s an unsupported configuration yet

1 Like

Hi Nathan,
CubeOrange is tricky do you have the pull down resistor on the TX line? With the pull down in place and SERIAL_OPTIONS=7 I have it working all right.

I had an R-XSR fully working, bidir as well with

  • RXSR_LBT_ACCST_191112.frk
  • RXSR-FPORT_LBT_ACCST_191128.frk
    and now same receiver flying with
  • RXSR_ACCESS_2.1.0.frsk
    not much luck with D16 2.x with the R-XSR but did not try 2.1.1 D16

Did you see this An Open Source Frsky Telemetry Script for the Horus X10,X12 and Taranis X9D,X9E and QX7 radios - #1425 by el_loco ?

I’ve given the 5k pulldown a shot. It’s not fully working with the RXSR or the Archer. I keep getting a cycling on-and-off telemetry for about a minute. Every 2 seconds it seems to reset. Then after a minute, the RC inputs freeze, the “sensor is lost” according to the transmitter, but the receiver is still powered and bound, and the TX shows full bars on RSSI. Unfortunately I can’t downgrade to ACCST because the X9-Lite is an ACCESS only transmitter. What do I need to do next?

Hi, please try version 1.9.5 stable, it should handle ELRS rssi all right

1 Like