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...
Replies
You'll need to "discover" the telemetry sensors on the radio before anything else. Then connect the radio to Companion and read the model from the radio.
This new sensor discovery thing, while great, requires that extra step of discovery physically the sensors and then copy to Companion to set up everything correctly.
Hi Luis.
The no message problem is Solved.
directory's ok,
But telemetry sensor settings were incorrect (T2 / Temp2 I think)
Is it possible to cut/paste telemetry settings into companion?
Tim
I don't see the way to do something like that from companion .
Thks
Hi All
I have been using Rolf Blomgren teensy adapter successfully for a year now
great work Thanks..
Then i decided to try updating to open tx 2.1.7 /"Cloony"/ latest lua.
Hmm big learning curve for an old pensioner!
nearly there now just a couple of issues
message sounds not playing (sanantha in /SOUNDS/en/TELEM)
(modes and system play ok)
and VFAS not displayed correctly on screen . (15v =1.5v??)
(lcd.drawNumber(30,13,getValue("VFAS"),DBLSIZE+PREC1)
I changed this line to this
lcd.drawNumber(30,13,getValue("VFAS")*10,DBLSIZE+PREC1)
Fixed! , May be we need a different version for every update of open Tx ?.
Thanks to all for making your efforts freely available to everybody
Tim
Hi
I assume that you've updated OpenTX to 2.1.7 from 2.0.x
If that is the case you also need to update the entire "native" collection of sounds of OpenTX.
Its not done in companion. Its done on the model Telemetry sensor screen on the Taranis. This is the screen on the Taranis where all your telemetry sensors are configured. If you have a sensor already called GPS, and it is displaying a string of digits instead of a regular Lat/Long notation, then, first delete this GPS sensor, then with your radio and craft powered, and your radio getting telemetry information through, choose the option on that same page called 'Discover new sensors' , and your GPS sensor (hosted by the Teensy) should re-appear on the screen. Once its there, then you can select 'Stop Discovery', and you should notice that the GPS sensor on that page is now showing more meaningful data - even if you don't have a satellite fix, if you select the GPS sensor and hit 'Ent' then it should show the format:
0º00'- 0º00'-
at the top of the edit screen.
I will seek to have the Wiki on github (https://github.com/Clooney82/MavLink_FrSkySPort/wiki/1.2.-FrSky-Tar...) updated to give better advice for setting this up.
Cheers, Paul
Kev, I really appreciate you taking the effort to check this. My GPS reading is what's wrong then. It appears ti be configured the same way as yours but maybe there is an issue dealing with the GPS values sent from the Mavlink side on APM 3.3. I may downgrade one of my lesser used quads to test this. Thanks again, Paul
Thanks
Kev,
The difference could be the APM version. I am also using EU version 2.1.6 OpenTx and have the GPS sensor setup on the Taranis Plus the same way as you. I used to use the OpenTx 2.0.x version of this telemetry code (on OpenTx 2.0.17) and that worked perfectly (I did tend to rely on the radar display quite a bit when I got disoriented with the crafts orientation), but the 2.1 version on 3.3. seems to have this one issue for me.
(for info - there are actually other issues with the LUA code generally (all versions) which I have been discussing and doing some testing with Clooney82's -next version of the code, these centre around Taranis memory structure limitations which Clooney is looking into separately, but they only effect the storage of values entered into the offset screen The ranges of values allowed are restricted at present due to these taranis limitations - I hope to see some interesting modifications before long to remove these limitations).
If you do decide to make the move to APM 3.3, bear in mind that there are new sound files from OpenTx required to be put on your SD card, plus 3.3. specific sound files supplied with the Clooney82 telemetry code too. The latest version has these telemetry specific sound files in a separate /SOUNDS/EN/TELEM sub directory to keep them distinct.
Cheers again Kev, Paul
Hi,
I am new to this project and would like to know if there is any tutorial showing how to compile and upload the files to the Teensy. Thanks in advance.
Zeek
-
34
-
35
-
36
-
37
-
38
of 186 Next