> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/sth/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/sth/setup/payload-manager.md).
# Payload Manager
This section explains the functionality of the Payload Manager.
The Payload Manager provides an overview of the installed payloads and allows you to edit their settings. It also displays the offset of the main battery in the nose of the vehicle, with the option to adjust the value. Additionally, you can enable or disable the white navigation lights on the Evo's wing tips.
* Power up the vehicle and the GCS.
* Open the WebUI: [10.41.1.1:5001](http://10.41.1.1:5001/) after a connection between the Evo and the GCS has been established.
{% hint style="warning" %}
The Payload Manager can be used to verify whether all payloads are registered by the system. Payloads integrated by DeltaQuad are preconfigured and require no additional changes. For Custom Payload Kits, relevant values can be added in the Payload Manager for the respective payload. The nose battery offset is set during production and only needs to be adjusted if hardware in the avionics bay is changed.
{% endhint %}
---
# 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/sth/setup/payload-manager.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.
