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
Oh bugger, cheers... its MavLink_FrSkySPort-s-c-l-v-rc-opentx2.1
Hey I did follow your instruction here.
And I went to this github: https://github.com/chsw/MavLink_FrSkySPort
But I found some issues there. And I made a fix by https://github.com/chsw/MavLink_FrSkySPort/issues/26
But now I am asking this: does teensy 1.0 support this feature? I am not having any teensy until now. But the compiling on different teensy boards has been valid. So can I assume teensy 1.0 board can do this MavLink_FrSkySbus work?
Thanks!
yes and no!
it work also on arduino pro mini and teensy2. but you need software serial on one message bus. also parsing severity messages is limited because less memory on pro mini and teensy < 3 boards.
/g
wolke
I saw people from here talk discussing whether this work on arduino pro mini or teensy. I have a arduino pro mini by side. Haven't known where to find the code which is suitable for arduino pro mini (software serial on one message bus and etc.. ). Do you think this project/product works? As what he claimed, that was for Arduino nano.
The latest project is by far only compatible with teensy 3.1 or later, which I don't have yet.
Do you know whether the project compatible with arduino pro mini is?
Thanks!
Hi all,
currently some of later involved developers create an collaboration on github to improve the project and make it available for opentx2.1.x. and also apm3.3. in moment we work on porting to opentx2.1.x. apm3.3 improvements will follow. for example new 3.3 severity messages.
please visit https://github.com/Clooney82/MavLink_FrSkySPort .
BUT before we are ready to release our first version, we have to clear LICENSE questions. we open an issue to discus this. please see https://github.com/Clooney82/MavLink_FrSkySPort/issues/29 .
we do not want to make errors here. so my question and an request at all developers which are involved and create code and media files (circuit diagrams, snd-files, how- too txt files), please visit our project on github and check if we currently use some files which we can not put under an proper license.
on the code side we are based on this history, most is github:
* Original Author: Jochen Tuchbreiter (2013) under (GPL3) https://code.google.com/p/telemetry-convert/
* Improved by: (2014) Rolf Blomgren & (2014) Christian Swahn https://github.com/chsw/MavLink_FrSkySPort
(2014) Luis Vale https://github.com/lvale/MavLink_FrSkySPort
(2015) Michael Wolkstein https://github.com/wolkstein/MavLink_FrSkySPort
(2015) Fnoop Dogg https://github.com/fnoopdogg/MavLink_FrSkySPort
(2015) Jochen Kielkopf * https://github.com/Clooney82/MavLink_FrSkySPort
Luis, Jochen, Fnoop Dogg, and me Michael aka Wolke are currently contribute to the new github project.
on the media side we plan to use CC license. we have a lot of images, tables and how-to text in our wiki, beside the small images and all the snd-files for taranis sd card structure.
it is important that each one who create media files also agree to this. else we have to remove this files and create new ones.
especially i mean some circuit diagrams and snd-files. many snd-files come from Luis which is also involved, but to ensure that we really not overlook something PLEASE contact us, or more easy, contribute to this ISSUE https://github.com/Clooney82/MavLink_FrSkySPort/issues/29
/g
wolke
Thanks!
https://github.com/Clooney82/MavLink_FrSkySPort
This looks very neat.
I am getting there.
HI, could anybody explain where to get and how to augment list of WAV files to support new messages from 3.3 rc10 and rc11 to accommodate all new set of changes including one below?
Have anybody looked at that issue yet?
---------------
Copter-3.3-rc11 is now available through the mission planner’s beta firmwares link.
This has just one change from –rc10, instead of saying “Waiting for 3D Fix” during pre-arm it gives a detailed reason like “PreArm: Need 6 sats (have 5)”.
--------------
See my reply at the beta thread.
and a bit more to elaborate: The code running on the teensy has to be redone to cope with that.
pre-arm checks are actually speaking up fine in RC10, what is missing now is a series of new messages for 'bad ahrs', 'compass variance', 'velocity variance', etc.
from what I understand those messages still fit old pattern of specific codes so it can be linked into WAV files same way as before, we only need a more complete correct list.
'need 3d fix' message replacement with what is done in RC11 is probably an issue, but if it has same old code I hope it would not matter. or do you mean there are no codes anymore for any messages?
These were effective at the time
Workbook4.xlsx
-
47
-
48
-
49
-
50
-
51
of 186 Next