> 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/ground-control-station-gcs/remote-identification-rid.md).
# Remote Identification (RID)
This section explains how to configure RID on the GSC.
{% hint style="info" %}
If RID is required, it will be configured by DeltaQuad during the calibration process. No further action is needed from the operator to activate RID. Please follow the steps below to enable broadcasting of the GCS’s location.
{% endhint %}
1. Connect the USB-GPS module to the Toughbook.
2. Open Auterion Mission Control (AMC).
3. Open the **Vehicle Overview** by clicking on **Vehicle Status** in the upper-left corner of AMC.
3. Open the **RemoteID** tab and verify that the Status is **Operative**.
{% hint style="danger" %}
If the GPS location of the GCS is not available, the **Vehicle Status** will be **red**, and arming is not possible.
{% endhint %}
{% hint style="warning" %}
There is an option to **use a fixed station position**. The operator must verify that this option complies with the laws and regulations of the country where the vehicle is operated. For example, in the United States, using a fixed position is not allowed. A continuous update of the GCS location must be provided.
{% endhint %}
When using the fixed station position option, the operator must provide the **latitude**, **longitude**, and **altitude** of the GCS.
---
# 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/ground-control-station-gcs/remote-identification-rid.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.
