> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/payloads/vio/case-study/gremsy-vio-x-if800/starting-the-vio.md).

# Starting the Vio

## Startup

Starting with the **drone powered OFF** and the red lever in the unlock position, attach the gimbal to the dovetail connector on the bottom side of the drone and lock the red lever in place.

Power on the controller, open the Herelink Settings and IGC applications. Then power on the drone and allow the startup sequence to run. Initialization will take approximately 1 minute.

When initialization is complete, you will see the Vio action menu populate on the right side of the screen. The HDMI video feed will display camera settings in green on the left side of the screen.

The camera is NOT set up to trigger photo captures during an automated mission.


---

# 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.gremsy.com/payloads/vio/case-study/gremsy-vio-x-if800/starting-the-vio.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.