> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/gov/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/gov/maintenance/diagnostics-report.md).

# Diagnostics report

The following section describes how to compile and download the diagnostics report.

In some cases, it might be necessary to provide a diagnostic report of your DeltaQuad Evo for further analysis of the flight performance and overall functionality. 

For this, you will need:

* A USB-A to USB-C cable
* A USB-A to USB-C adapter (provided with the DeltaQuad Evo)
* The DeltaQuad Evo with a flight battery
* A laptop

1. Remove the hatch of the DeltaQuad Evo. Above the avionics bay, where the hatch's closing mechanism and the LCD are located, you will find a USB socket.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/HjY4U5mq1ycbxzWShD9h/image.png" alt=""><figcaption></figcaption></figure>

2. Install the USB-A to USB-C adapter, which is included in your vehicle's accessories. In some cases, it may already be plugged into the USB socket.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/03NGZ2aA5LoX2tboK2dQ/image.png" alt=""><figcaption></figcaption></figure>

3. Connect the USB cable to the USB-C connector.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/YOqkif04turKkhDVxLkI/image.png" alt=""><figcaption></figcaption></figure>

4. Connect the other end of the cable to your laptop.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/lZt51zq8O9neMKWlIQxz/image.png" alt=""><figcaption></figcaption></figure>

* Power on the laptop.
* Power on the DeltaQuad Evo.

{% hint style="warning" %}
Power on the DeltaQuad Evo only after connecting the USB cable to both, the vehicle and the laptop.
{% endhint %}

5. On the laptop open a browser and type in the following address: **<http://10.41.1.1>**

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/q26Fy9291EOJMqHJJ2xC/1.webp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If your computer can't connect to the vehicle after following the steps above, please try a different USB cable.
{% endhint %}

6. Scroll to the bottom of the page and click on **Show additional information**.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/wcAtlCamyvoyHdp10cUs/2a.png" alt=""><figcaption></figcaption></figure>

7. In the right corner at the bottom of the page click on **Download diagnostic report**. The report will be generated.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/C9niYz88jnEvJs9DAkOR/3a.webp" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/InHuRpdHHEyDb7RJetLU/4.png" alt=""><figcaption></figcaption></figure>

8. After the report has been generated a download will commence. You will find the diagnostics report in the download folder of your system.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/OdVXLkzWxRl6LvPYSSbH/5.webp" alt=""><figcaption></figcaption></figure>

Please share the diagnostics report with the DeltaQuad support team 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/gov/maintenance/diagnostics-report.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.