FrSky X (D16)
Protocol Number: 15 Autobind: No Channel Re-mapping: No Extended Limits: Yes Failsafe Support: Yes Receiver Match: Yes Telemetry: Yes Option Value: Frequency fine tuning
Frequency tuning is required for this protocol. See the Frequency Tuning page for more details.
Models: FrSky D16 receivers, including X4R, X6R, X8R, XSR, XM+, and SxR, running ACCST v1 firmware. D16 compatible receivers.
FrSky receivers running ACCST v2 firmware should use the FrSkyX2 protocol - they are not supported by this protocol.
Full telemetry is supported, including bi-directional capabilities, enabling LUA scripts to be used to configure SxR receivers and Betaflight parameters (for example).
Listen Before Talk (LBT) is supported. Use the EU/LBT sub-protocols for receivers running EU / LBT firmware.
In OpenTX the FrSky X protocol is accessed as FrSky, with subprotocol D16.
The FrSky protocol also has subprotocols for ACCST v1 D16 receivers in FCC and EU/LBT modes and D16 8 channel mode, as well as FrSky V receivers and FrSky D (D8) receivers.
When binding a D16 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.
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.
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.
FCC protocol, 16 channels @18ms.
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 |
FCC protocol, 8 channels @9ms.
CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |
CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |
EU-LBT (listen before talk) protocol, 16 channels @18ms.
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 |
EU-LBT (listen before talk) protocol, 8 channels @9ms.
CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |
CH1 | CH2 | CH3 | CH4 | CH5 | CH6 | CH7 | CH8 |
Uses the identifier learnt from another FrSky radio using the FrSkyRX/CloneTX mode. 16 Channels
Uses the identifier learnt from another FrSky radio using the FrSkyRX/CloneTX mode. 8 Channels
