# FrSky R9

## Details

**Protocol Number:**  65\
**Autobind:**  No\
**Channel Re-mapping:**  No\
**Extended Limits:**  Yes\
**Failsafe Support:**  Yes\
**Receiver Match:**  Yes\
**Telemetry:**  Yes\
**Option Value:**  N/A

## Notes

**Models:**  FrSky R9 receivers

{% hint style="danger" %}
R9 receivers must be running ACCST Flex firmware
{% endhint %}

{% hint style="info" %}
Only supported on MULTI-Modules which have an **SX1276 RF** module, e.g. the Jumper T18 Pro Internal 5-in-1 module.
{% endhint %}

### Binding

#### OpenTX <= 2.3.9

During binding the receiver will be configured to output channels 1-8 on the PWM pins, with telemetry on.

#### OpenTX >= 2.3.10

When binding an R9 receiver the radio will prompt you to choose the bind configuration.  This prompt allows you to configure the receiver outputs, in the same way that it can be configured with physical jumpers placed on the PWM output pins during bind.

![R9 Binding](https://3357080223-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LwnWq9OVxVlVodwNBnH%2F-MCHQTiHjJcGhZktCPoL%2F-MCHUAD-lQV7Cbpucrue%2Fr9-binding.png?alt=media\&token=4bc6218e-5335-47fc-b473-563c1001d39b)

The selection you make determines which channels will be output on the PWM pins of the receiver, and whether telemetry is on or off.  The remaining channels will be output on the SBUS port.

#### For Example:

`Ch1-8 Telem ON` will output the radio channels 1-8 on the receiver's PWM pins and channels 9-16 on the SBUS port, with telemetry enabled.  This configuration could typically be used on a model with servos connected directly to the receiver.

`Ch9-16 Telem ON` will output the radio channels 1-8 on the SBUS port and 9-16 on the receiver's PWM pins, with telemetry enabled.  This configuration could typically be used on a model with a flight controller connected to the SBUS port and accessories (such as a camera gimbal) connected to the PWM pins.

Refer to your receiver documentation for more information.

## Sub Protocols

### 0 - R9\_915

915MHz, 16 channels.

| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |

### 1 - R9\_868

868MHz, 16 channels.

| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |

### 2 - R9\_915\_8CH

915MHz, 8 channels.

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

### 3 - R9\_868\_8CH

868MHz, 8 channels.

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

### 4 - R9\_FCC

FCC, 16 channels.

| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 | CH9 | CH10 | CH11 | CH12 | CH13 | CH14 | CH15 | CH16 |

### 6 - R9\_FCC\_8CH

FCC, 8 channels.

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


---

# 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-r9.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.