> 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/deltaquad-evo-enterprise-edition.md).

# DeltaQuad Evo Enterprise Edition

DeltaQuad Evo Enterprise Edition eVTOL UAV is a limitation-breaking aerial solution for civilian and semi-government use.

{% hint style="info" %}
Version number of this document: v2.0-27.06.2024
{% endhint %}

<figure><img src="https://814155445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAPQBdKMBlJjf93sVHGiP%2Fuploads%2FLZFXuuGPLoHPKbov8nbj%2FEvo%20Enterprise_OM%20Header.png?alt=media&amp;token=6e0ab550-34fa-42cc-bd53-30cfdc0630bc" alt=""><figcaption></figcaption></figure>

DeltaQuad Evo is a fixed-wing eVTOL UAV that has set new standards in the drone world. Longer flight times, extended transmission ranges, and increased payload flexibility are all available in Evo Enterprise Edition. Its advanced features make it ideal for mapping and surveillance missions like infrastructure inspection, precision agriculture, safety monitoring, or light cargo transportation.

Evo Enterprise edition is designed for civilian and semi-government use. It operates based on the DeltaQuad Controller on the world-wide license free 2.4Ghz band and offers radio options up to 30 km range.


---

# 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/deltaquad-evo-enterprise-edition.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.