> 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/flight/deltaquad-controller/pairing-the-deltaquad-controller-with-the-air-unit.md).
# Pairing the DeltaQuad Controller with the air unit
In this section, we will discuss how to bind the DeltaQuad Controller with the DeltaQuad Evo air unit.
{% hint style="info" %}
After a factory reset has been performed on the DeltaQuad Controller, it might be necessary to rebind the controller with the air unit located in the DeltaQuad Evo. Please follow the steps below.
{% endhint %}
1. Power on the DeltaQuad Evo and the DeltaQuad Controller. Open Auterion Mission Control. In the upper right corner of the screen, the Radio icon is located. If it has a strike-through and the radio link is not available, a rebinding is required.
2. Remove the hatch of the avionics bay by loosening the two screws with a Torx tool (T10).
{% hint style="warning" %}
Please use a medium-strength lock bond when tightening the screws again.
{% endhint %}
3. In the avionics bay you will see the radio modem. Push the *SET* button. This puts the modem into the bind mode. When in bind mode, the LED of the modem rotates through different colors.
4. On the Controller, open the Radio Settings app.
5. Open *WIRELESS PARAMETER CONFIGURATION*.
6. Tap on *FREQUENCY MATCHING*.
7. Click on *Confirm*.
After the binding process has been successful, a connection will be established between the DeltaQuad Evo and the DeltaQuad Controller.
---
# 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/flight/deltaquad-controller/pairing-the-deltaquad-controller-with-the-air-unit.md?ask=&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.
