# Bench Test

This section details how to validate that Cyclops is operational before executing test flights. We will initialize the Cyclops system and expect the drone to be in a flight-ready state before 

At this stage of the integration process you have:

* Physically integrated Cyclops on your vehicle [Vehicle Integration](/cyclops/vehicle-integration.md)
* Configured ArduPilot for Cyclops [Autopilot Integration](/cyclops/autopilot-integration.md)

{% hint style="warning" %}
You will need a Windows/Linux laptop with [Vozilla GCS](/gcs-software/vozilla-gcs.md) installed in order to proceed. 
{% endhint %}

We recommend that you go through the documentation for [Vozilla GCS](/gcs-software/vozilla-gcs.md) to familiarize yourself with using Cyclops before proceeding.

## Before Powering On

You must generate a map of your flight area before testing Cyclops on your UAV. Refer to [Creating a new map](/gcs-software/vozilla-gcs/maps/creating-a-new-map.md)in the Vozilla GCS app documentation for details on this process.

## Booting the Vehicle

Power on your UAV and Cyclops system. Ensure that your camera and flight computer both boot properly.

## Initialize Cyclops

Connect your laptop to the flight computer using the Ethernet port. Open the Vozilla app on your laptop.

The first step will be to upload your map(s) and set the home position on Cyclops from the [Maps](/gcs-software/vozilla-gcs/maps.md) tab. Refer to [Selecting a map](/gcs-software/vozilla-gcs/maps/selecting-a-map.md) and [Setting a home position](/gcs-software/vozilla-gcs/maps/setting-a-home-position.md) for more information on these operations.

### Verify Data Connectivity

Verify the camera connection on the compute module by navigating to the [System](/gcs-software/vozilla-gcs/system.md) tab.

<figure><img src="/files/ZrUppkAPRRK8Z1qAbL2q" alt=""><figcaption></figcaption></figure>

You can use the SNAPSHOT button to verify the image is up-to-date and not occluded

<figure><img src="/files/Qt25ugTit3gDgbaCiqVh" alt=""><figcaption></figcaption></figure>

Verify the MAVLink connection on the compute module by navigating to the [System](/gcs-software/vozilla-gcs/system.md) tab.

<figure><img src="/files/Qy260n8RApc1SIYWgfua" alt=""><figcaption></figcaption></figure>

Connect to the VPS Edge Device. \
The default URL is `tcp:192.168.218.100:14559`

<figure><img src="/files/VS8DKTAc5J5FpriLuqB9" alt=""><figcaption></figcaption></figure>

You should see MAV information from your drone displayed. \
If you do not see an autopilot, verify your wiring and baud rate. \
The default baud rate is 921600.

### Update Active Maps

On the [Maps](/gcs-software/vozilla-gcs/maps.md), ensure the correct map is selected.

<figure><img src="/files/7LElvAhR30GRCID6LG0s" alt=""><figcaption></figcaption></figure>

### Update Launch Location

Set the home position to the location where you will be launching your UAV by dragging the marker or entering manually.

### Restart VPS

Return to the main dashboard and restart Cyclops by clicking the "*Restart*" button under VPS Control.

<figure><img src="/files/zw2M1p7WeYRqQGZZHnyF" alt=""><figcaption></figcaption></figure>

The dashboard should now show that the system is **Running**.

At this point you can expect:

* Cyclops to be connected to the autopilot over MAVLink.
* Cyclops is receiving data from the camera.

{% hint style="success" %}
Cyclops is running and all required systems are healthy on Vozilla.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.theseus.us/cyclops/validation/bench-test.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.