> 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/safety-features/rc-loss-failsafe-trigger-advanced-mode.md).
# RC Loss Failsafe Trigger (Advanced Mode)
This section covers the RC Loss Failsafe Trigger settings.
{% hint style="warning" %}
This setting can be ignored. The RC Loss Failsafe Trigger can remain unchanged, as the DeltaQuad Evo GOV uses only a virtual RC link, not a physical one.
**To configure the Failsafe Action for a loss of communication, the appropriate actions must be selected for the Data Loss Failsafe Trigger.**
{% endhint %}
The **RC Link Loss Failsafe Trigger** controls the behavior of the vehicle when the RC link is lost.
**Default Failsafe Action:** Return mode
**Default RC Loss Timeout:** 5 s
---
# 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/safety-features/rc-loss-failsafe-trigger-advanced-mode.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.
