# Autopilot Telemetry (Python)

## Introduction <a href="#introduction" id="introduction"></a>

The `get-telemetry-python` is an application written in Python and using mavsdk to get telemetry from the flight controller (over mavlink) and print the data to the standard output.

This application is composed of one Docker container based on `auterion/ubuntu-python-mavsdk:0.15.0`. This base image is itself based on Python Duster ARM64V8 and contains essential build dependencies to build Python software. It also contains mavsdk python framework v0.15.0.

Our container Dockerfile is really simple, first we copy our python script, then, using the command `ENTRYPOINT`, we define the startup command that Docker will use to start our container.

## Commands <a href="#commands" id="commands"></a>

You can build the application by running the following command:

```
make build
```

It will create an app artifact in `output/get-telemetry-python.auterionos`.

After a successful build, you can connect your Skynode with USB-C and run the following command to install the application on your device:

```
make install
```

You can monitor the application execution by ssh into the device (ssh root\@10.41.1.1) and run the following command:

```
docker logs get-telemetry-python
```

You can stop and remove the application with the following commands:

```
cd /data/app/get-telemetry-python/src 
docker-compose stop 
docker-compose rm -f 
docker rmi get-telemetry-python
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.auterion.com/app-development/legacy-app-workflow/examples/get-telemetry-python.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.