Replies

  • In FrSkySPort.ino the integer ap_longitude and ap_latitude are divided by 100 and the result multiplied by 6 before sending to the SPort. I understand oring with 0x80000000 to set bit 31 high, but why the arithmetic? The photo of the Taranis shows the Lat and Long displays as degrees and MM.MMMM. Is the Taranis taking an integer and doing the conversion internally?

    Roger

    • This is the code on the Taranis for the conversion:

           

                   gps_long_lati_b1w = (gps_long_lati_data&0x3fffffff)/10000;

                  gps_long_lati_a1w = (gps_long_lati_data&0x3fffffff)%10000;

            switch ((gps_long_lati_data & 0xc0000000)>>30) {

            case 0: {

                      frskyData.hub.gpsLatitude_bp = (gps_long_lati_b1w/60*100)+(gps_long_lati_b1w%60);

                      frskyData.hub.gpsLatitude_ap = gps_long_lati_a1w;

              frskyData.hub.gpsLatitudeNS = 'N';

              }break;

            case 1: {

                      frskyData.hub.gpsLatitude_bp = (gps_long_lati_b1w/60*100) + (gps_long_lati_b1w%60);

                      frskyData.hub.gpsLatitude_ap = gps_long_lati_a1w;

              frskyData.hub.gpsLatitudeNS = 'S';

              }break;

          .........

       

  • Hey can you please make a simple tutorial on hot to set up the taranis for this, i have flasheed the teensy and soldered the pins and plugged the teensy into telem port and smart port but there is no telemetry displaying on the taranis???

    • It is in your radio manual setup section. Just set up you telemetry pages by adding new parameters to display.

      I posted exactly the same question here but figured it out in 5 minutes later and removed my question.

      • I have added every single choice to my taranis screen all but rssi display data that is changing.

        A1 says 4.76

        and T1 and T2 say 32 but even say this when the teensy is disconnnected

  • Kent, Do you know the exact syntax, so I can put it in MavLink_FrSkySPort.ino?

    regards Peter

    • Hi Peter.  I was showing you generally how to do what you would need to do.  Much more has to happen in the code for it to do what you want.  When the message you are after comes back you have to then direct the pertinent data to the FrSky port in the proper way.  The best way is to jump in and figure it out.  C is not terribly hard and there is plenty of help out on the internet and here.

  • Hi Rolf

    Thanks again for this great code.

    I got the flight mode to be sent down via your suggestion.  Thanks for the info.  Right now I am sending the mode down as the fuel telemetry value.  Is there are more appropriate value to send it down as?  Where did you get the values for the FrSky DATA ID's.

    • Just an FYI for anyone who is trying this.  I got the mode number to be sent to the Taranis via the fuel telemetry value.  That all works.  However, at present there is no way I could find to get the Taranis to create custom switches that triggered on the fuel value in order to trigger the functions to play the voice files.  

      The issue is that you have to use the a~x,a>x,a<x functions to trigger the switch, where a is the fuel value and x is a constant.  Unfortunately a~x is meant to deal with things like RC inputs where you dont really want to trigger on a single value as much as its close to this value  As such, a trigger for say mode 3 (fuel ~= 3) will trigger on several other values because they are close.

      I submitted an issue on the OpenTx git hub site to add an a=x function in addition to the a~x function that exists now.  The response from OpenTx was that that feature was already incorporated into version 2.0 of OpenTx.  If anyone has thought of another way to do it let me know.  Otherwise I will continue to trigger off of the physical switches to get the mode rather than the telemetry value until OpenTx 2.0 is released

      • You have tried fuel>2 and fuel<4 ? I think you can have two conditions?

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…