> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/evo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltaquad.com/evo/auterion-suite/activating-your-vehicle.md).

# Activating your vehicle

The following section describes how to activate your DeltaQuad Evo.

Activating your vehicle will connect it to Auterion Suite. This will allow you to access cloud features and manage your vehicle remotely.

**To activate a vehicle:**

1. Make sure the Evo is powered off.
2. Connect your vehicle to your computer via USB-C.
3. Power your vehicle.
4. Open a browser on your computer and navigate to the vehicle's WebUI:[ 10.41.1.1](http://10.41.1.1/)

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2FW5SY0hea6HD2ErUcaimP%2Fimage.png?alt=media&amp;token=b6981123-facf-40dd-8a2b-1c827183cb21" alt="" width="335"><figcaption></figcaption></figure>

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2F2wM04Vl1SyU7RnZlEo2n%2Fimage.png?alt=media&amp;token=34fdeb20-4c44-4816-b012-99611c046bd7" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
To activate a vehicle make sure your vehicle is connected to the Internet using Auterion Mission Control > Connectivity tab.
{% endhint %}

4. Click on **Activate now** or **Scan the QR code**.
5. You will be directed to Auterion Suite, where you'll see this pop-up window to activate your Skynode.

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2FLyZ30e5UXnCGHMrjLGit%2Fimage.png?alt=media&amp;token=8336a74d-e044-4f11-b917-d85cc82d2293" alt="" width="563"><figcaption></figcaption></figure>

6. Click on Activate and your vehicle will be visible under **Fleet Management** > **Vehicles**.

### Rename a vehicle <a href="#rename" id="rename"></a>

1. Select a vehicle from the All Vehicles list.
2. Click on Rename vehicle in the top bar.

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2FFevzt6Z6RMiRwSN09K4i%2Fimage.png?alt=media&amp;token=2a2de5c7-460a-42dc-9c57-75e036a6aa87" alt="" width="375"><figcaption></figcaption></figure>

3. Enter the new vehicle name and click on Rename Vehicle.

### Vehicle Identity <a href="#identity" id="identity"></a>

A vehicle is a collection of parts. An airframe, a Skynode, a flight controller, and more. These various pieces of the vehicle make up the complete "vehicle identity."

To view the serial numbers and IDs of the components associated with a given vehicle, click the "fingerprint" button near the vehicle's name on the *Vehicle Page*.

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2FPxApiobDm01DMqoMNyML%2Fimage.png?alt=media&amp;token=e144f5bf-7bb1-42fe-900f-d847510014fc" alt="" width="296"><figcaption></figcaption></figure>

This will open up a window that shows all of the IDs of the components that make up the vehicle in the Suite. Each ID controls a specific component. For example, the flight controller ID is how the logs coming out of a flight controller as associated with the vehicle page in the Suite.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.deltaquad.com/evo/auterion-suite/activating-your-vehicle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
