# MAVSDK example program on VOXL 2 not running

Source: https://forum.modalai.com/topic/3445/mavsdk-example-program-on-voxl-2-not-running
Category: VOXL SDK and Software (https://forum.modalai.com/category/47/voxl-sdk-and-software)
Tags: voxl-sdk
Posted: 2024-05-16 20:00:34 UTC by achanana
Replies: 1 · Views: 710

## achanana · 2024-05-16 20:00:34 UTC

Hello,

I am working with the Starling (QRB5165 VOXL 2 running sdk-1.2.0). I am trying to follow the [voxl-docker-mavsdk-cpp](https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-cpp) tutorial to get the takeoff and land script to work.

I was able to get the docker server running and pulled the MAVSDK image. However, I get the following error when trying to execute the takeoff and land script:
```
root@m0054:/home/MAVSDK/examples/takeoff_land#  ./takeoff_and_land udp://:14551
[03:15:33|Info ] MAVSDK version: 0.28.0 (mavsdk_impl.cpp:26)
[03:15:33|Debug] New: System ID: 0 Comp ID: 0 (mavsdk_impl.cpp:377)
Waiting to discover system...
No system found, exiting.
```
This is the output I got from voxl-inspect-services:
```
voxl2:~$ voxl-inspect-services 
Scanning services...

 Service Name             |  Enabled  |   Running   |  CPU Usage
-------------------------------------------------------------------
 docker-autorun           | Disabled  | Not Running |  
 modallink-relink         | Disabled  | Not Running |  
 voxl-camera-server       |  Enabled  |   Running   |    90.9%
 voxl-cpu-monitor         |  Enabled  |   Running   |     0.4%
 voxl-dfs-server          | Disabled  | Not Running |  
 voxl-feature-tracker     | Disabled  | Not Running |  
 voxl-flow-server         | Disabled  | Not Running |  
 voxl-imu-server          |  Enabled  |   Running   |     3.8%
 voxl-lepton-server       | Disabled  | Not Running |  
 voxl-mapper              | Disabled  | Not Running |  
 voxl-mavcam-manager      |  Enabled  |   Running   |     0.0%
 voxl-mavlink-server      |  Enabled  |   Running   |     2.6%
 voxl-modem               | Disabled  | Not Running |  
 voxl-neopixel-manager    | Disabled  | Not Running |  
 voxl-open-vins-server    | Disabled  | Not Running |  
 voxl-portal              |  Enabled  |   Running   |     0.7%
 voxl-px4-imu-server      |  Enabled  | Not Running |  
 voxl-px4                 |  Enabled  |   Running   |    24.6%
 voxl-qvio-server         |  Enabled  |   Running   |    34.3%
 voxl-rangefinder-server  | Disabled  | Not Running |  
 voxl-remote-id           | Disabled  | Not Running |  
 voxl-softap              |  Enabled  |  Completed  |  
 voxl-static-ip           | Disabled  | Not Running |  
 voxl-streamer            |  Enabled  |   Running   |     0.0%
 voxl-tag-detector        | Disabled  | Not Running |  
 voxl-tflite-server       |  Enabled  |   Running   |     3.1%
 voxl-time-sync           | Disabled  | Not Running |  
 voxl-uvc-server          | Disabled  | Not Running |  
 voxl-vision-hub          |  Enabled  |   Running   |     2.6%
 voxl-wait-for-fs         |  Enabled  |  Completed  |  

```
Do you have any idea what might be the issue here? Should voxl-px4-imu-server be running? Could that be the issue?

Thanks for your help!

## Reply by Moderator (ModalAI staff) · 2024-05-17 02:48:07 UTC

@achanana said in [MAVSDK example program on VOXL 2 not running](/post/16949):
> voxl-px4-imu-server

is for the Qualcomm Flight RB5 architecture and is not relevant to Starling

It is likely your voxl-mavlink-server is not configured properly. MAVSDK communicates with the port opened up in voxl-mavlink-server