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: 307531


Reply to This

Replies to This Discussion

Super Rolf, works perfectly.
Thank you for your effort.
This is a great project.

I hope you have more good ideas.


One more question:
If the message is not received, whatever the reason.  Shall the message repeated?


The message is only sent the first time a battery failsafe triggers.


Then let us hope that the message is always heard.

Hi Rolf, after flashing my taranis last Saturday, distance and speed are finally shown, so if anyone experiences any issue of this sort, good idea to update the taranis. 

Sorry Rolf, I didn't see this message, only when decided to report on the previous issue.

may be via a custom switch+custom function and show a bitmap graphics+ play a wave file? 

I think everyone could do whatever he prefers as long as the code is received by Taranis :D

also, would it be possible add a direct pass through of the APM mode code to taranis? there are some beta flight modes with numbers ranging above 13....  for example I like to fly in the beta "hybrid" mode which, even though is still a beta, offers valuable advantages but its number is 14.  search "hybrid mode" on this forum for more info. 

Rolf, could you also add a failsafe message to be sent as a code to taranis: i.e. GPS failsafe 1, fence failsafe 2, battery failsafe 3. 

also useful but not critical: cpu load, baro health, gps health

p.s.  just learned that teensy 3.1 has hardware DAC, so it is possible to skip those FSK modems, it will be needed to use 3.1 as  a ghettostation controller on the ground though. even though not suitable for complex auto missions LTM might prove very useful for FPV flights where bidirectional link is not necessary. so anyone could build an open source antenna tracker  which also works with APM and doe not require a PC to run it!  all with 2 x teensy 3.1 boards. most importantly it would be easily expandable. 

There is a limitation of channels on the telemetry.  You can select the data to be sent to the Taranis on each channel by editing the code, but not all channels are interpreting the data as a straight number, so this will also impact what can be sent.

Hi Rolf, I´m new here and I have a problem with the combination Taranis/APM 2.5/Teensy 3.1 and the FrSky Sensor FCS-40A. In the display from the Taranis I see everythink like Alt or GAlt, Hdg or VSpd.

The only problem are the dates from the FCS-40A like Volt or Ampere, these dates comes not clear since installing the teensy. The dates are springing from zero to the wright measur.

Do you know what is the reasing????

The Taranis sees  both the FCS-40 and the APM sending data for current and voltage,

In the code for the Teensy3.1 you have to remove  the sending of this data ( current and voltage).

You can try the attached file.



Rolf, when I try to compile, I get the follwing mistake:

MavLink_FrSkySPort.ino:47:25: fatal error: GCS_MAVLink.h: No such file or directory
compilation terminated.

Can you help me?

Reply to Discussion



Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service