Hi all,

I just bought an FrSky Taranis for my quad copter and needed to get the Mavlink data up on the Taranis LCD telemetry display. So here is my solution using a Teensy3.1 as a converter between MavLink and the S.Port on FrSky X8R.

See attached file below...

Views: 311310


Reply to This

Replies to This Discussion

OrangeRX 433 with openLRSng or others firmware support RSSI report.

You could get the reference from the bottom of this URL https://github.com/openLRSng/openLRSngWiki/wiki/Settings-Guide 

I use pixhawk, the RSSI pin is S.Bus and set it for 3.3v range.

It's not real signal, it is packet loss rating. 


I have modified your led 2.0 version to simplify the cabeling on my copter. Also have a modified led_Control.ino to make it work. I am not a skilled hacker, but I have a lot of spare time....

Hi all

Just to remember all that there are changes being made on both platforms, i.e. OpenTX with the future 2.1.2 and specially ArduPilot that even this week had a big change on reporting that might/will affect all the "translators" https://github.com/diydrones/ardupilot/commit/767b4da5b6852a2ba700e....

There will be a future development on Arducopter that will replace/add to the error messages to error codes.

I would like to bring to everyones attention a project that might replace our Teensy's and our MinimOSD's. https://sites.google.com/site/alceosd/

The project at the moment has no support to handle the FrSky but it is quite easy to add it, and the lead developer is open to further enhancements. https://github.com/diydrones/alceosd

MHO this project combines the needs we have with on the fly telemetry.

so that is one board combining teensy 3.1 and minim osd connected to s.port ?

looks nice

but hope you wont abandon the old project... 

LoL, no

all the code developed to "decode" Mavlink can be used on both platforms, and the Lua scripts would be the same.

Something else that will significantly influence the current libraries and scripts are the newer SensorID's that could be used, instead of reusing inappropriate sensorID's like RPM and Temp...

Great work, can you share it with me, so I can add it to github.

Maybe open an issue on github with link to the code.

Hello, please anyone have .hex file for teensy 3.1 without current and voltage readings for opentx 2.1?  I use Frsky FLVSS and FCS-150A.

Yes, I know but how do you get the mavlink rssi to display  on taranis, did you modify the teensy f/w to listen for mavlink rsssi  and pack into one of the frsky variables? If so which command did  you use to get rssi oout if the mavlink streem and which "container" variable are you using? 


Stupid question. I understand how you connect the serial (tx/rx) to the Teensy from the OrangeRx on the ground side, but where does the S Port output of the Teensy connect to in the Taranis? Sorry I am not getting that part. On the UAV side it plugs into the S Port. 

And I presume it can use all the same LUA scripts without modification.

I think he is using X8R on the ground to retranslate communications.

You got a message...


added it to led-control and s-c-l-v-rc-opentx2.1 branch.



Reply to Discussion


© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service