> 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/camera-setting-menu/camera-definition-file-download.md).

# Camera Definition File Download

<figure><img src="https://3309772875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnikHUDUd2JXqkOsnOi7l%2Fuploads%2FUeKlDgINj2L0CV4E1aNs%2Fintergration.png?alt=media&amp;token=cc63eb9d-a69a-457e-806e-b2b199068577" alt=""><figcaption></figcaption></figure>

## Method 1: Online

{% stepper %}
{% step %}

#### Step 1: Download the Camera Definition File

The GCS connects to the Internet to download the camera definition file from the Gremsy Server. **Guide to Connecting Herelink Remote to Wi-Fi**

* Video guide link [here](https://youtu.be/q8sj71Yjg8M)

{% hint style="info" %}
For the 1st time, it is needed
{% endhint %}
{% endstep %}

{% step %}

#### Step 2: Save the File Locally

Once the download is complete, the camera definition file is automatically saved to the local storage of the GCS.
{% endstep %}

{% step %}

#### Step 3: Use the Locally Stored File

The GCS can continue using the locally stored camera definition file even when an Internet connection is unavailable.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Note:** If the payload software is updated and a new camera definition file becomes available, reconnect the GCS to the Internet and download the updated file.
{% endhint %}

## Method 2: Offline

{% hint style="info" %}
No Internet connection is available, but an Ethernet connection between the GCS and the payload is available.
{% endhint %}

{% stepper %}
{% step %}

#### Step 1: Connect via Ethernet

Connect the GCS to the payload using an Ethernet cable.
{% endstep %}

{% step %}

#### Step 2: Retrieve the Camera Definition File URL

The payload provides a URL to access the camera definition file hosted on its local server.
{% endstep %}

{% step %}

#### Step 3: Download and Save Locally

The GCS accesses the provided URL, downloads the camera definition file from the payload, and saves it to local storage for future use.
{% endstep %}
{% endstepper %}

## Method 3: Manual Offile

{% hint style="info" %}
The GCS has no Internet connection and cannot connect to the payload via Ethernet.
{% endhint %}

{% stepper %}
{% step %}

#### Step 1: Download the Camera Definition File

Download the required camera definition file from the Gremsy GitHub repository, or contact <support@gremsy.com> to request the file.
{% endstep %}

{% step %}

#### Step 2: Copy the File to the QCS Folder

Once the download is complete, copy the camera definition file into the `Parameters` folder used by QGroundControl (QGC).

**Example folder path:**

`Documents > QGroundControl > Parameters`

After copying the file, open QGroundControl and verify that the camera definition file is available for use.
{% endstep %}
{% endstepper %}


---

# 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/camera-setting-menu/camera-definition-file-download.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.