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
did you check serial port settings? port 2 speed may be set to 115kbit.
Both are exactly the same, checked twice. And I pressed this buttion in Mission Planner "Enable OSD Telemetry". And Flight Mode does pass to both OSD and SPort. Is it different from other MavLInk messages?
got a lot of error compiling the files on Arduino IDE 1.0.5..
i also use arduino 1.0.5. make sure that all library dependency's are correct. reading the error messages will give you the answer. also you have to setup SERIAL for pro mini correctly. as default it is configured to compile on teensy2.
see readme.md here https://github.com/wolkstein/MavLink_FrSkySPort/tree/s-c-l-v-rc/Mav...
/g
wolke
Yes. Wolke created a version: https://github.com/wolkstein/MavLink_FrSkySPort/tree/s-c-l-v-rc/HEX
it was adjusted.
you need to get it all from peter king`s google drive page.
https://drive.google.com/folderview?id=0B-B7PQy0joGrUjFmb2pSTFlqcWc...
I hope this link will work. go into radio, taranis, advanced. teensy code in there is matched properly with a lua script that gives very nice stats. you may want to edit that script to disable power alarm if you did not make custom resistor contraption for power level. I do not think it is needed at all, my system works fine without it and I get voltage and amperage just fine.
what is awesome is that gps based arrow that shows where your drone is pointed to. it is very convenient.
hi, i am wolke. need more infos about gps reading problems on my fork. what goes wrong there.
/g
wolke
I am not sure. I guess it stems from the fact that Paul referred someone to a modified version of your code for Teensy 2 that resides in someones Google Drive after I referred then to your github repository. I remember there being some back and forth about GPS coordinates so I was wondering of this was what was 'fixed' in Peter King's changes. I do tend to point people to your fork so I just thought that IF it was the case that there is a slightly modified version of your fork then maybe the changes should live in your fork and not on someones Google drive! Hope that helps.
ok, on teensy2 and pro mini code was a problem with negative cords. this is already fixed in my teensy2&pro_mini branch. thx for pointing out.
/g
wolke
-
79
-
80
-
81
-
82
-
83
of 186 Next