# FrSky D (D8)

## Details

**Protocol Number:**  3\
**Autobind:**  No\
**Channel Re-mapping:**  No\
**Extended Limits:**  Yes\
**Failsafe Support:**  No\
**Receiver Match:**  Yes\
**Telemetry:**  Yes\
**Option Value:**  Frequency fine tuning

{% hint style="danger" %}
Frequency tuning is required for this protocol.  See the [Frequency Tuning page](/using-the-module/frequency-tuning.md) for more details.
{% endhint %}

## Notes

**Models:** FrSky receivers D4R and D8R. DIY RX-F801 and RX-F802 receivers. D8 compatible receivers.

Telemetry enabled for A0, A1, RSSI, TX\_RSSI, TX\_LQI and Hub. Lower TX\_LQI indicates a better quality link and is a good indicator of how well the module is tuned.

{% hint style="success" %}
In OpenTX the FrSky D protocol is accessed as **FrSky**, with subprotocol **D8**. 

The **FrSky** protocol also has subprotocols for [FrSky V](/using-the-module/protocol-details/frsky-v.md) receivers, [FrSky X (D16)](/using-the-module/protocol-details/frsky-x.md) receivers in FCC and EU/LBT modes and D16 receivers operating in 8 channel mode.
{% endhint %}

## Channel Assignment

| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |

## Sub Protocols

### 0 - D8

FrSky D8 protocol, using the MULTI-Module's own unique ID.

### 1 - Cloned

Use the identifier learnt from another FrSky radio when binding with the [FrSky RX protocol in CloneTX mode](/using-the-module/protocol-details/frsky-rx.md#1-clonetx).

{% hint style="warning" %}
When using the Cloned sub-protocol, the **Receiver Number** cannot be used any more and is ignored.
{% 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://www.multi-module.org/using-the-module/protocol-details/frsky-d.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.