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

Attachments:

Reply to This

Replies to This Discussion

Thanks Gary I appreciate you helping me out! 



Garry Kraemer said:

> Here is sort of a big picture. When I connect my Taranis to my computer via usb it shows up as two entities. Taranis and > Taranis2... is this normal?

Yes, do not mess with the EPROM or FIRMWARE on that 'mounted' device.

> On TARANIS it has the EPROM and FIRMWARE  the other Taranis2 has the SD card contents with all the items copied > over . I copied my models to the models folder as well. And yet when I go to the telemetry page down to page1 it
> says there are no scripts.?? I don't understand why even with the SD card removed from the TX when turned on it still > shows all my models ??

The models you fly and modify are contained in the transmitter.  Consider the files on the SDCard as your backups.  If you modify a model in the Transmitter, make sure you backup the changes to the SDCard.

> Sorry I know a lot of my problem is my lack of knowledge about how the Taranis all works.. You just make the Lua code I > know. I'm just stuck don't know what to try next.

Make sure you have 'LUA' enabled in the FIRMWARE load you are running in the Taranis.  The first page has 'LUA' and it MUST be checked and the firmware downloaded and loaded into the Taranis for LUA to
function.



HTH.

Garry



Richard Kennedy said:

It seems like I have something going on with my radio. In fact it acts exactly the same wether I have the sd card in the radio or not! That can't be right.  BTW I added my models to the models folder after that screen dump showing the SD card. 



Richard Kennedy said:

Here is sort of a big picture. When I connect my Taranis to my computer via usb it shows up as two entities. Taranis and Taranis2... is this normal? On TARANIS it has the EPROM and FIRMWARE  the other Taranis2 has the SD card contents with all the items copied over . I copied my models to the models folder as well. And yet when I go to the telemetry page down to page1 it says there are no scripts.?? I don't understand why even with the SD card removed from the TX when turned on it still shows all my models ?? Sorry I know a lot of my problem is my lack of knowledge about how the Taranis all works.. You just make the Lua code I know. I'm just stuck don't know what to try next. 

Paul Atherton said:

Richard, traveling to French alps at moment, but as passenger I can take a look at your messages. Your Google Drive link seems to contain the SD card contents for Opentx 2.2-rc10. The rc11 version of Opentx just came out, so would suggest you upgrade. This new version has a new SD card download v6 so you will need this instead of the v5 version you have in Google Drive. Next you need to read the wiki which details what additional files from the project you need to add to the SD card contents. I provide replacement voice files for Opentx 2.2 in either the Available or Samantha voices (I find Ava to be the best one, and much nicer voice than the one provided in the OpenTx voice pack). Additionally, I provide voice files required for the telemetry project. The two choices are for either Ardupilot 3.2 or 3.3 (and newer). Again both available in either Ava or Samantha voice. You need to choose the correct version for your ardupilot version and add the required TELEM folder to the SD card SOUNDS/en folder you already copied. If you can tell me your version details for both Opentx and ardupilot, then I can put together the files you need in the Google Drive.

I went back to 2.1.9... copied your sd card files you did on my google link and it works great!!!!! You da man Paul!!!!!! 2-3 days I've been pulling my hair I REALLY appreciate your efforts to get me sorted out!!!! Best thing also is I can see what you did to the sd card files can compare with what I [ I have a copy on my Mac of course ] to see where I went wrong!! I think I'll just enjoy it working on 2.1.9 for awhile before the 2.2 switch as I know that requires another sd card structure. But I'm happy !! I love the layout of the script it tells you all you need / want to know in a great layout. Just awesome. Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

RK

Paul Atherton said:

Richard, I am in the process of uploading the entire SD card content for your setup to your Google drive. The folders under the path you sent me, should be placed on your SD card after first deleting everything you have there at present. It may take another 20mins or so for drive on my Mac to finish the upload, so maybe look at this tomorrow to make sure all has finished copying.

Just to answer one of your previous questions: it is correct that you see two drives appear when you connect the Taranis to your Mac. The first folder is called Taranis - this is actually the EEPROM memory of the taranis, and used only by Companion for its connection to your Taranis when you upload/download settings. The second drive that appears is the SD card itself. You can rename this if you want.

Cheers, Paul 

Man the lua script is awesome! I thought I was going to just have to deal with some quirks if I flew my plane but then I saw the 'Telemetry script configuration' all zi had to do was switch to plane ...SWEET!!!! All the flight mode call out correctly.. can change the units ... WOW!!! Way cool man I have to apologies about my offer obviously this is worthy of TWO blonds wink wink. LOL 

Paul Atherton said:

Richard, I am in the process of uploading the entire SD card content for your setup to your Google drive. The folders under the path you sent me, should be placed on your SD card after first deleting everything you have there at present. It may take another 20mins or so for drive on my Mac to finish the upload, so maybe look at this tomorrow to make sure all has finished copying.

Just to answer one of your previous questions: it is correct that you see two drives appear when you connect the Taranis to your Mac. The first folder is called Taranis - this is actually the EEPROM memory of the taranis, and used only by Companion for its connection to your Taranis when you upload/download settings. The second drive that appears is the SD card itself. You can rename this if you want.

Cheers, Paul 

Richard, yes, you said you were running OpenTx 2.1.9 and >AP3.3 so the files I compiled  were for those versions. If you need the files for 2.2 at any point then please ask and I can compile those also inside your Google Drive.

Enjoy!

I was in the telemetry screen - Sensors down to sensor 7 and bumped something now it reads [0.0ft] Funny thing is sensor 29 is reading correctly. Any idea how to reset sensor? The reason I was in there looking was the altitude seems to fluctuate a LOT way out of sync with reality. I would think it's just a quirky baro but the alt reading on GCS reads correctly so not sure what going on with that. Thoughts? 

Richard, not entirely sure what you mean. Maybe best to delete and rediscover the sensors - follow the wiki page for instructions etc on calculated sensor addition and various tweaks. It's probably easier than figuring which sensors you have configured incorrectly.

Thanks I'll give that a try

Paul Atherton said:

Richard, not entirely sure what you mean. Maybe best to delete and rediscover the sensors - follow the wiki page for instructions etc on calculated sensor addition and various tweaks. It's probably easier than figuring which sensors you have configured incorrectly.

I did get it back to normal thx! Guess I'll need to ask over at the apm forum what they are using to calculate altitude. Maybe they use a combo of baro and gps to come up with a more accurate reading that just the baro. It's like it way too sensitive. If I lift it up 3 feet it says it went up 10 or more. It reads much more accurately on my GCS. Interestingly enough is it also seems to read correctly on my Taranis in the 'home' screen as show in my second pic. So it much be using a different source or some combination. In any event it's definitely different than shown in the Lua screen. I'll check out the wiki also for "on calculated sensor addition and various tweaks." Thanks again for all the work you and other have done. Sure wish there was a 'contribute' or 'Donate' button! I help out on a monthly basis for the arducopter /plane crew every month. Don't be too modest if there is one for this Lua and I missed it please let me know! 



Paul Atherton said:

Richard, not entirely sure what you mean. Maybe best to delete and rediscover the sensors - follow the wiki page for instructions etc on calculated sensor addition and various tweaks. It's probably easier than figuring which sensors you have configured incorrectly.

Richard,

The telemetry screen uses the 'Alt' telemetry sensor, so you need to check that this sensor has been configured correctly as per the wiki (https://github.com/athertop/MavLink_FrSkySPort/wiki/1.2.-FrSky-Tara...). Like this:

A fresh discovery should have set this up correctly. Is it possible you may have adjusted the Ratio value or the unit of measure - on the OpenTx model sensor telemetry screen this should be set to metres regardless of what altitude value you choose on the LUA telemetry screen configuration.

The value on the main OpenTx model home screen is based on the telemetry sensor you choose on the telemetry sensors model configuration screen:

Also, I see you are using feet on the telemetry screen where the value in the GCS is likely to be set to metres.

Ah yes... I had ft selected as the unit. Seems fine now thank you.



Paul Atherton said:

Richard,

The telemetry screen uses the 'Alt' telemetry sensor, so you need to check that this sensor has been configured correctly as per the wiki (https://github.com/athertop/MavLink_FrSkySPort/wiki/1.2.-FrSky-Tara...). Like this:

A fresh discovery should have set this up correctly. Is it possible you may have adjusted the Ratio value or the unit of measure - on the OpenTx model sensor telemetry screen this should be set to metres regardless of what altitude value you choose on the LUA telemetry screen configuration.

The value on the main OpenTx model home screen is based on the telemetry sensor you choose on the telemetry sensors model configuration screen:

Also, I see you are using feet on the telemetry screen where the value in the GCS is likely to be set to metres.

Hi

    I'm not sure if this the correct place to post but here goes.

I have been successfully been using the teeny converter and the lua script which uses "re purposed" data very succesfuly

with arducopter 3.3  Thanks to all developers.

I have upgraded to arducopter 3.4 and notice that pass through protocol is an option.

i tried this and my taranis discovered many new sensors  so far so good .

now my question is how do i modify my lua scrips to understand this new pass through sensor/protocol.

I searched around and not found little information except for flight deck.

I f any one could point me in the right direction I would be grateful

Thanks Tim

Tim,

The Teensy project is written specifically to provide Mavlink->SmartPort telemetry conversion, so only deals with the Pixhawk being configured to send out Mavlink over the telemetry port and so it is not designed as it stands to deal with the new passthru protocol. The new protocol would not actually require a teensy at all, but just a telemetry inverter, and by adding one of these and selecting the passthru protocol, as you suggest, the Taranis would see lots of new telemetry sensors, but unfortunately the LUA screens as they stand are not coded for these sensors, and to make this work, would involve a lot of research and coding, which I just don't have the time to do at this point. To be honest, this is of no practical use for my model setup in any case, as I use ULRS instead of FrSky Tx/Rx and I have the mavlink data sent over the ULRS radio link where I connect it into Mission Planner on the ground, but secondly I also have the mavlink feed on the ground connected to the teensy where it converts and feeds into the Taranis to provide the usual screens. So in my case sending down the passthrough protocol would be of no use as it would take away the Mavlink capability I would need for Mission planner.

If you wanted to understand the passthrough protocol to develop your own LUA screens then I would suggest looking into the Ardupilot code where I believe the protocol is documented. This protocol was written by the guys at Craft & Throry to allow their commercially available LUA screens to function, so maybe that solution would be better in your case if you really want to take the passthrough protocol route.

If you do develop something, please let us know on the forum as I would be interested in any progress.

Cheers and good luck, Paul 

Tim Painter said:

Hi

    I'm not sure if this the correct place to post but here goes.

I have been successfully been using the teeny converter and the lua script which uses "re purposed" data very succesfuly

with arducopter 3.3  Thanks to all developers.

I have upgraded to arducopter 3.4 and notice that pass through protocol is an option.

i tried this and my taranis discovered many new sensors  so far so good .

now my question is how do i modify my lua scrips to understand this new pass through sensor/protocol.

I searched around and not found little information except for flight deck.

I f any one could point me in the right direction I would be grateful

Thanks Tim

Reply to Discussion

RSS

© 2017   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service