> 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/connecting-a-second-gcs.md).

# Connecting a Second GCS

This section explains how to connect a secondary GCS to the primary GCS.

{% hint style="success" %}
You can connect a secondary GCS to the primary GCS using a Wi-Fi network, a hotspot, or a USB connection. A secondary GCS on-site is useful when both a camera operator and a pilot are needed.
{% endhint %}

## Wi-Fi Connection - Prerequisites

* DeltaQuad Evo and the GCS must be powered on.
* A connection between the vehicle and GCS must be established.
* A laptop or any other device with AMC installed.
* The primary and secondary GCS must be connected to the same Wi-Fi network or hotspot.

***

1. On the primary GCS, open the **Evo Control Panel** app located on the desktop.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/PmmmktIsRRXPrWzh5MRv/Evo%20Control%20Panel.webp" alt="" width="126"><figcaption></figcaption></figure>

2. The **Evo Controller** window will open. Copy the **WiFi IP address**—in our case, 192.168.2.105.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/eDYRzBSzBkSmGkBPxyZo/Evo%20Control%20Panel%202.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/IAEzUrPIfiswccFx4C3w/Evo%20Control%20Panel%202a.webp" alt="" width="563"><figcaption></figcaption></figure>

3. On the secondary GCS, open AMC. Navigate to **AMC Menu > Settings > Comm Links**. Click on **Add**.

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

4. Enter the following items and click **OK**.

* **Name:** Enter any name
* **Type:** UDP
* **Listening Port:** 14550
* **Target Host:** \<Wi-Fi IP adress>:5760
  * In our case 192.168.2.105:5760

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/jwWiVKLHvoAKc35oFpMj/Add%202.webp" alt=""><figcaption></figcaption></figure>

5. Click on the newly created comm link and **Connect**.

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

6. After a few seconds the secondary GCS connects to the primary  GCS. The vehicle status should be indicated in the upper left corner of AMC.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/GYQjri12sASAqe0Qap8D/Connect%202.webp" alt=""><figcaption></figcaption></figure>

***

## USB Connection - Prerequisites

* DeltaQuad Evo and the GCS must be powered on.
* A connection between the vehicle and GCS must be established.
* A laptop or any other device with AMC installed.
* The primary and secondary GCS must be connected via a USB cable.

***

1. On the primary GCS, open the **Evo Control Panel** app located on the desktop.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/PmmmktIsRRXPrWzh5MRv/Evo%20Control%20Panel.webp" alt="" width="126"><figcaption></figcaption></figure>

2. The **Evo Controller** window will open. Copy the **USB IP address**—in our case, 192.168.42.129.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/EiAixwpbnmYmA84um5Bu/USB%20Evo%20controller.webp" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/7kC08QCuqEYzSLWHhIKl/USB%20IP.webp" alt="" width="563"><figcaption></figcaption></figure>

2. On the secondary GCS, open AMC. Navigate to **AMC Menu > Settings > Comm Links**. Click on **Add**.

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

4. Enter the following items and click **OK**.

* **Name:** Enter any name
* **Type:** UDP
* **Listening Port:** 14550
* **Target Host:** \<USB IP adress>:5760
  * In our case192.168.42.129:5760

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/0nUnqfEfgijJlhsFMAjO/Add%20USB.webp" alt=""><figcaption></figcaption></figure>

5. Click on the newly created comm link and **Connect**.

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

6. After a few seconds the secondary GCS connects to the primary  GCS. The vehicle status should be indicated in the upper left corner of AMC.

<figure><img src="https://content.gitbook.com/content/KBsYYYTTfla4fXzYBpU6/blobs/GYQjri12sASAqe0Qap8D/Connect%202.webp" alt=""><figcaption></figcaption></figure>


---

# 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/connecting-a-second-gcs.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.
