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

Attachments:

Reply to This

Replies to This Discussion



Paul Hammond said:

Hey Paul.

Im a bit happier.... I think i have it working, I used the MavLink_FrSkySPort.ino from github (although i assume this doesnt include your fixes/improvements you mentioned in the previous post) and uploaded it to the teensy using Arduino IDE. The reason i did this was so that i could change #define _MavLinkSerialBaud  to 115200 so that i can use it with the ULRS orangeLRS system which sends mavlink data over 433mhz as well as control signals, I have a x4r running CPPM firmware which also allows access to the SPort.

Paul,

I finally got around to getting a ULRS setup and now have it working.  I setup an almost identical repeater configuration as you. As I couldn't get hold of any of the OrangeRx LRS modules (discontinued by HK I believe) I bought the Wolfbox system instead from BG. I have bluetooth (for Mission Planner connectivity) and the teensy integrated (for the Taranis Telemetry) - actually managed to fit the Teensy inside the Wolfbox JR module case, and have wired it internally.

I'm really glad you mentioned the baud rate - I think I would have been head scratching there for a while to figure that out! I have the SWR displaying correctly in my telemetry screen in the Taranis. To be honest, the SWR has nothing to do with teensy of course - its simply the SWR from the Taranis internal XJT antenna.

My next step is to get RSSI telemetry sorted out. The regular RSSI shown in telemetry on the Taranis with this repeater setup is of course the RSSI between the Taranis->X4R (on the repeater) so of no real value for a flight. So need to somehow get the RSSI from the ULRS Rx feeding into the Pixhawk - and somehow integrated into the Teensy code so we can get it displayed on the Taranis.

As for getting the single LiPo cell value (C-min) displayed in the telemetry screen - because I no longer have the option to use the FLVSS (FrSky S.Port LiPo) monitor in my model, this useful data is not directly available any more. There is however a work-around in the teensy code which can be employed to simulate this single cell voltage - it simply takes the VFAS and divides it by the number of cells present - not perfect but at least allows this piece of telemetry to display something (albeit not really showing the lowest cell value). To enable this, in MavLink_FrSkySPort.ino, on line 132, you will see a commented out line:

//#define USE_FLVSS_FAKE_SENSOR_DATA                      // Enable  if you want send fake cell info calculated from VFAS, please set MAXCELLs according your Number of LiPo Cells

Just un-comment that line (remove // from the start), and also check down to line 186, where you should enter your LiPo Cell count (#define MAXCELLS 3). In my case this is 4.

So have you been flying with this repeater setup? How reliable has it turned out? I have noticed some lag on mine with control inputs - very slight but not quite as snappy as the native FrSky 2.4 system. You tested radio failsafe triggers RTL correctly?

Thanks again for your post. Paul

@Paul Atherton. I am using ULRS now and looking to use it exclusively. But I still really want the Mavlink telemetry on my Taranis. I understand that sensor polling is is why we need an X series receiver and cannot use a Teensy on on the ground side and hence have to relay with an X series receiver. Have you seen that pawelsky on RCGroups has now created a data polling in his S Port sensor encoding classes that run on a Teensy. http://www.rcgroups.com/forums/showthread.php?t=2245978

It strikes me that we can now use a Teensy on the ground side in the JR port of a Taranis instead of using a repeater. I think this may be the Holy Grail for me. I have six of these (mini ULRS with USB designed by Artemen). 

I will have a go at this but you might find this easier than I to merge into the existing project. 

If we could get this working this could also be used with a Dragonlink V3 or even with a regular 3DR Sic radio.

@Paul A I have some modified OrangeRX modules (voltage boosted for 1W) output that have been tested. I now have better boards for ULRS (form factorwise anyway). PM me and I can donate them to you if you are still looking for some ULRS action. And maybe you can figure out how to integrate sensor polling into the Teensy so we can do away with X receiver relaying.

Marc, I don't think it's solely sensor polling to get that solution working. I think there would have to be some changes in opentx also as presently it only listens to telemetry input on the external bay input if D16 is selected and a bind is in place. I think to have it accepting data on the s.port pin with Ppm input selected, we would need changes in Opentx.

Very kind of you to offer the OrangeRX units. To be fair, I'm doing OK with the Wolf box units just now, and don't see me using ULRS outside of my fx-61 wing, although that might change so will definitely bear your offer in mind. Cheers, Paul

No worries. Did not realize you had the Wolfbox units. I will see if I can open a request with OpenTx devs tonight. It seems to me to be an easy change.



Marc Dornan said:

No worries. Did not realize you had the Wolfbox units. I will see if I can open a request with OpenTx devs tonight. It seems to me to be an easy change.

Cheers Marc. I agree, an easy change. Was trying to get my head around the FrSky telem libraries mentioned in your earlier post. They look interesting, but not exactly sure how the polling thing would be implemented in the setup we are using. Looks like its required from the decoder end (would usually be done by the Tx unit), as it mentions s.port being a 'pull' protocol. I maybe need to look again when I have more free time. Good find though! Its incredible how resourceful the RC community is. Its great to be a part of it.

Thanks again, Paul

p.s. those Artemen boards look awesome!



Paul Atherton said:



Marc Dornan said:

No worries. Did not realize you had the Wolfbox units. I will see if I can open a request with OpenTx devs tonight. It seems to me to be an easy change.

Cheers Marc. I agree, an easy change. Was trying to get my head around the FrSky telem libraries mentioned in your earlier post. They look interesting, but not exactly sure how the polling thing would be implemented in the setup we are using. Looks like its required from the decoder end (would usually be done by the Tx unit), as it mentions s.port being a 'pull' protocol. I maybe need to look again when I have more free time. Good find though! Its incredible how resourceful the RC community is. Its great to be a part of it.

Thanks again, Paul

p.s. those Artemen boards look awesome!

Marc, forgot to mention - the Teensy code actually is using those libraries you referred to earlier and it does use the sensor polling call mentioned in the article - so it already does the polling (from the encoder side). Cheers

Hello ! I would like

I've look around and can't find the answer to whether there is a way to change the Units displayed on the Taranis for altitude and speed from metric to imperial?

Thanks

Not without doing a conversion in the lua script
  • Thanks for the clarification. Those Artemen boards are fantastic. ULRS is really moving along now. Next up will be the all in one JR board with Bluetooth. I funded this first batch to move things along. I cannot understand why HK does not start making them. 

Paul Atherton said:



Paul Atherton said:



Marc Dornan said:

No worries. Did not realize you had the Wolfbox units. I will see if I can open a request with OpenTx devs tonight. It seems to me to be an easy change.

Cheers Marc. I agree, an easy change. Was trying to get my head around the FrSky telem libraries mentioned in your earlier post. They look interesting, but not exactly sure how the polling thing would be implemented in the setup we are using. Looks like its required from the decoder end (would usually be done by the Tx unit), as it mentions s.port being a 'pull' protocol. I maybe need to look again when I have more free time. Good find though! Its incredible how resourceful the RC community is. Its great to be a part of it.

Thanks again, Paul

p.s. those Artemen boards look awesome!

Marc, forgot to mention - the Teensy code actually is using those libraries you referred to earlier and it does use the sensor polling call mentioned in the article - so it already does the polling (from the encoder side). Cheers

I'm having a problem with Airspeed (ASpd)

I have Mission planner set to Metric, if I blow a constant speed of air into the pitot tube missionplanner shows around 17m/s. Taranis is showing only around 7m/s in the lua script and if I look at the raw data on the telemetry setup screen it also shows around 7m/s.

What am I missing?

Thanks

Reply to Discussion

RSS

Groups

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

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service