Replies

    • 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!

        FrSky/OpenTx to Ground Station as a relay · Issue #31 · Clooney82/MavLink_FrSkySPort
        I saw that the Rx on teensy 3.1 board has not been used yet. The teensy board is only used to translate MavLink protocol to FrSky OpenTx. It&#39;s on…
  • 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

    Clooney82/MavLink_FrSkySPort
    This MavLink_FrSkySPort repository is discontinued! The development is moved to athertop/MavLink_FrSkySPort. Please do not use this repo, and follow…
    • Thanks! 

      https://github.com/Clooney82/MavLink_FrSkySPort 

      This looks very neat.

       I am getting there.

      Clooney82/MavLink_FrSkySPort
      This MavLink_FrSkySPort repository is discontinued! The development is moved to athertop/MavLink_FrSkySPort. Please do not use this repo, and follow…
  • 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

          • hmm, it is odd as in my current sounds directory I have messages up to code 125.

            this spreadsheet does seem to end at 98 - ready to track.

            I always assumed codes come directly from ardupilot firmware - is it a wrong assumption? is it a teensy code alone that assigns a specific numerical code to a message?

            • There's a second spreadsheet that I couldn't attach that covers those codes.

              And the sounds are most likely the ones I've created on a Mac using either AVA or ALLISON synthetic voice.

              The codes are generated at the Teensy, where a translator function checks the text message sent by Ardupilot and maps that message to a code that is sent on the OpenTX telemetry link, because sending the entire text messages over the OpenTX telemetry link was not viable.

              The parser is here:
              https://github.com/lvale/MavLink_FrSkySPort/blob/DisplayAPMPosition...

              lvale/MavLink_FrSkySPort
              This MavLink_FrSkySPort repository is discontinued! The development is moved to Clooney82/MavLink_FrSkySPort where we work together on this. Please d…
This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
21 hours ago
DIY Robocars via Twitter
21 hours ago
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…