ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VOXL ESC FPV queries

    ESCs
    4
    32
    1187
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Jetson NanoJ
      Jetson Nano @Alex Kushleyev
      last edited by

      @Alex-Kushleyev I currently use, VOXL2 USB 3.0 Expansion Adapter connected to VOXL2. From the UART7 port of the Expansion Adapter I have connected to 6-PIN Telemetry1 Port in Flight Core V2.

      My connection is similar to this,
      a976cc01-f06c-4080-b2dc-a551ef614cce-image.png

      As you mentioned earlier, I'm establishing connection through port /dev/ttyHS1. When I run the cat command to read the messages from this port, I get garbled data as below,

      646c42a2-3edd-4b18-aecd-c0a36af3721e-image.png.

      I'm not exactly clear when you mean if I have tried connecting to VOXL2 from QGC and access the Flight Core V2. Few things I have tried is,

      • Connecting to FlightCore V2 by connecting to Wifi of VOXL2. I also have a Wifi setup on VOXL2, which also acts as my Telemetry line. From QGC I connect to this local network to access FC data and PX4 parameters on Flight Core V2.

      • I have tried and tested few mavlink message commads which communicate with PX4 directly for C2C.

      1 Reply Last reply Reply Quote 0
      • Jetson NanoJ
        Jetson Nano @tom
        last edited by

        @tom As per your response on shifting to voxl-inspect-mavlink mavlink_offboard, I see that even in mavlink server documentation from ModalAI that service pipeline is not listed. Is it that something that has to be explicitly be enabled somewhere?
        Even as per the documentation, I dont see this service pipeline listed.

        0abeaffd-4404-446e-9b9b-a1c2ab30b668-image.png

        tomT 1 Reply Last reply Reply Quote 0
        • tomT
          tom admin @Jetson Nano
          last edited by

          @Jetson-Nano I could have the naming wrong. If you inspect mavlink_onboard what kind of data do you see?

          Jetson NanoJ 1 Reply Last reply Reply Quote 0
          • Jetson NanoJ
            Jetson Nano @tom
            last edited by

            @tom This is the output I get,

            Screenshot from 2025-01-16 20-49-20.png

            tomT 1 Reply Last reply Reply Quote 0
            • tomT
              tom admin @Jetson Nano
              last edited by

              @Jetson-Nano Since you don't have voxl-px4 running I think that data is likely coming from your external flight controller

              Jetson NanoJ 1 Reply Last reply Reply Quote 0
              • Jetson NanoJ
                Jetson Nano @tom
                last edited by

                @tom yes, the message is coming from external flight controller, Flight core v2. Now can you share how to double check if the RC message is set up to forward to voxl-mavlink-server from Flight Core (if not, how to enable it) and how to actually read that message?

                Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                • Eric KatzfeyE
                  Eric Katzfey ModalAI Team @Jetson Nano
                  last edited by

                  @Jetson-Nano Probably should also look at the pipe for messages from the flight controller to the GCS (Labeled mavlink_to_gcs in the above diagram but you'll have to double check that name). Generally the flight controller is configured with two mavlink streams. One is the onboard stream that has high rate messages and is intended for local use (e.g. on VOXL or VOXL 2) and the other is more the default settings for communication with a GCS. You can configure what each of these streams contain in PX4. You can add streams, change stream rates, etc. all via PX4 configuration. Please refer to the PX4 documentation for details on how to do this.

                  Jetson NanoJ 1 Reply Last reply Reply Quote 0
                  • Jetson NanoJ
                    Jetson Nano @Eric Katzfey
                    last edited by

                    Hi @Eric-Katzfey, I was thinking another approach, where we can use pymavlink to get the RC_channel data. Any inputs to the mentioned approach, is it feasible?

                    Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                    • Eric KatzfeyE
                      Eric Katzfey ModalAI Team @Jetson Nano
                      last edited by

                      @Jetson-Nano Yes, that should work. You should be able to send heartbeats from a Python script using pymavlink and connect to the flight controller via voxl-mavlink-server. Then you should start receiving all the normal messages sent out by the flight controller to the GCS which should include the RC channels message.

                      Jetson NanoJ 1 Reply Last reply Reply Quote 0
                      • Jetson NanoJ
                        Jetson Nano @Eric Katzfey
                        last edited by Jetson Nano

                        This post is deleted!
                        Jetson NanoJ 1 Reply Last reply Reply Quote 0
                        • Jetson NanoJ
                          Jetson Nano @Jetson Nano
                          last edited by

                          @Alex-Kushleyev can you check the above mentioned approach

                          Alex KushleyevA 1 Reply Last reply Reply Quote 0
                          • Alex KushleyevA
                            Alex Kushleyev ModalAI Team @Jetson Nano
                            last edited by

                            @Jetson-Nano , I am sorry, I don't have this hardware set up right now, so I can't actually test what you are trying to do. I will check with the team regarding who can test it.

                            Alex

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Powered by NodeBB | Contributors