> 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/maintenance/firmware-update.md).

# Firmware Update

This chapter explains the process for firmware and software updates.

When purchasing a DeltaQuad Evo, operators will be notified via email of relevant firmware updates for your vehicle and software updates for the Ground Control Station (GCS).

{% hint style="info" %}
The email notification contains a download link for the required firmware and software, instructions on how to perform the update, and a method to verify successful completion.
{% endhint %}

{% hint style="danger" %}
To keep the DeltaQuad Evo warranty intact, the firmware update must be performed within two weeks of receiving the email notification.
{% endhint %}

There are two different updates available.

## Update Your DeltaQuad Evo Firmware

In this update, the firmware of the DeltaQuad Evo flight controller needs to be updated.

## Update Auterion Mission Control

In this update, your DeltaQuad Evo Ground Control Station requires a software update.

If you have questions after receiving the update instructions, please contact our support at **<support@deltaquad.com>**.


---

# 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/maintenance/firmware-update.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.