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

    MAVSDK on local laptop

    VOXL SDK
    2
    3
    227
    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.
    • D
      dvPr1m3
      last edited by

      Hello,

      I have a Starling V2 drone and have been able to successfully execute the automated takeoff and landing MAVSDK example as described here:
      https://docs.modalai.com/mavsdk/#mavsdk-on-voxl2

      The drone is in station mode and both the drone and the ground control station PC (which is a laptop) have IPs assigned to them. I am able to ping the laptop from the drone and vice versa. QGroundcontrol works fine on the laptop. The laptop runs Ubuntu 22.04.

      I am looking to now deploy the same take off and landing example but executing it from within the laptop (instead of using the docker container on the drone). I used the Dockerfile within https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk.git as my reference to install the required packages for mavsdk and was able to build and install mavsdk and the C++ examples. However, when I try connecting to the drone at the IP and port 14550, MAVSDK is not able to connect to the drone.

      Any help would be greatly appreciated. Thanks!

      1 Reply Last reply Reply Quote 0
      • D
        dvPr1m3
        last edited by

        I got this working. I initially had the following in the takeoff_and_land.py script which did not work:

        await drone.connect(system_address="udp://192.168.1.44:14550")

        where 192.168.1.44 was the IP address of the drone, but when I changed it to the line below it worked!

        await drone.connect(system_address="udp://:14550")

        The IP address of my laptop is 192.168.1.100 and is listed as "primary_static_gcs_ip" in /etc/modalai/voxl-mavlink-server.

        My question though is how does the script on my laptop know that the drone is located at 192.168.1.44 in the second case and why does the first case where I specify the host within the connect() call not work?

        Thanks!

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

          Hey @dvPr1m3 , How were you able to do it on VOXL 2?

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