> 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/setup/deltaquad-evo-battery/empty-payload-box.md).
# Empty Payload Box
This section will discuss the empty payload box and its functionality.
Every DeltaQuad Evo comes with an empty payload box.
Before takeoff, the payload bay must be fully loaded with either two single payload boxes or one double payload box. Otherwise, the OLED screen above the avionics bay will display one of the following messages:
No payloads found
Slot 1: No payload
Slot 2: No payload
If payload slot 1 is occupied by, for example, the Raptor 360, then payload slot 2 must be filled with the empty payload box that comes with every DeltaQuad Evo.
{% hint style="info" %}
The vehicle will not initialize if the payload bay is either not fully loaded or incorrectly loaded.
{% 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/gov/setup/deltaquad-evo-battery/empty-payload-box.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.
