Protocols details

July 29, 2026 · View on GitHub

Here are detailed descriptions of every supported protocols (sorted by RF modules) as well as the available options for each protocol.

If you want to see examples of model configurations see the Models page.

The Deviation project (on which this project was based) have a useful list of models and protocols here.

Useful notes and definitions

  • Surface and air protocols - As the list of supported protocols grows even the STM32 ARM microcontroller cannot hold all of the protocols. Firmware available from the Multi-Module website has been split into two groups, surface "SFC" and air "AIR". You can check which protocols are included in each of these groups in the Validate.h source file.
  • Channel Order - The channel order assumed in all the documentation is AETR. You can change this in the compilation settings or by using a precompiled firmware. The module will take whatever input channel order you have choosen and will rearrange them to match the output channel order required by the selected protocol.
  • Channel ranges - A radio output of -100%..0%..+100% will match on the selected protocol -100%,0%,+100%. No convertion needs to be done.
  • Extended limits supported - A channel range of -125%..+125% will be transmitted. Otherwise it will be truncated to -100%..+100%.
  • Italic numbers are referring to protocol/sub_protocol numbers that you should use if the radio (serial mode only) is not displaying (yet) the protocol you want to access.
  • Autobind protocol - The transmitter will automatically initiate a bind sequence on power up or model/protocol selection. This is for models where the receiver expects to rebind every time it is powered up. In these protocols you do not need to press the bind button at power up to bind, it will be done automatically. In case a protocol is not autobind but you want to enable it, change the "Autobind" or "Bind on channel" on OpenTX setting to Y for the specific model/entry.

Bind on channel feature

  • Bind on channel can be globally enabled/disabled in _config.h using ENABLE_BIND_CH. Any channel between 5 and 16 can be used by configuring BIND_CH in _config.h. Default is 16.
  • Bind on channel can be locally enabled/disabled by setting "Bind on channel" or "Autobind" per model for serial or per dial switch number for ppm.
  • Once activated, any bind will only happen if all these elements are happening at the same time:
    • Bind on channel = Y
    • Throttle = LOW (<-95%)
    • Bind channel (16 by default) is going from -100% to +100%
    • It's recommended to combine the bind switch with Throttle cut or throttle at -100% to drive the bind channel. This will prevent to launch a bind while flying and enable you to use the bind switch for something else.

Protocol selection in PPM mode

The protocol selection is based on 2 parameters:

  • selection switch: this is the rotary switch on the module numbered from 0 to 15
    • switch position 0 is to select the Serial mode for er9x/erskyTX/OpenTX radio
    • switch position 15 is to select the bank
    • switch position 1..14 will select the protocol 1..14 in the bank X
  • banks are used to increase the amount of accessible protocols by the switch. There are up to 5 banks giving acces to up to 70 protocol entries (5 * 14). To modify or verify which bank is currenlty active do the following:
    • turn on the module with the switch on position 15
    • the number of LED flash indicates the bank number (1 to 5 flash)
    • to go to the next bank, short press the bind button, this action is confirmed by the LED staying on for 1.5 sec

Here is the full protocol selection procedure:

  1. turn the selection switch to 15
  2. power up the module
  3. the module displays the current bank by flashing the LED x number of times, x being between 1 and up to 5
  4. a short press on the bind button turns the LED on for 1 sec indicating that the system has changed the bank
  5. repeat operation 3 and 4 until you have reached the bank you want
  6. power off
  7. change the rotary switch to the desired position (1..14)
  8. power on
  9. enjoy

Notes:

  • The protocol selection must be done before the module is turned on
  • The protocol mapping based on bank + rotary switch position can be seen/modified at the end of the file _Config.h**

Serial mode

Serial mode is selected by placing the rotary switch to position 0 before power on of the radio.

You've upgraded the module but the radio does not display the name of the protocol you are loking for:

  • erskyTX:
    • Place the file Multi.txt (which is part of the MPM source files) on the root of your SD card.
    • If the entry still does not appear or is broken, upgrade to version R222d2 or newer.
  • OpenTX:
    • Upgrade to the latest version of OpenTX.
    • If still not listed, use the Custom entry along with the protocol and sub_protocol values indicated by the italic numbers under each protocol. You'll find a summary of the protocols and numbers to use in table below.

Available Protocol Table of Contents (Listed Alphabetically)

Protocol NameBuildProtocol NumberSub_Proto 0Sub_Proto 1Sub_Proto 2Sub_Proto 3Sub_Proto 4Sub_Proto 5Sub_Proto 6Sub_Proto 7RF ModuleEmulation
AssanAIR/SFC24NRF24L01
BayangAIR/SFC14BayangH8S3DX16_AHIRDRONEDHD_D4QX100NRF24L01XN297
Bayang RXAIR/SFC59MultiCPPMNRF24L01XN297
BlueFly95NRF24L01
BugsAIR41A7105
BugsMiniAIR42BUGSMINIBUGS3HNRF24L01XN297
Cabell34Cabell_V3C_TELEM----F_SAFEUNBINDNRF24L01
CFlieAIR38CFlieNRF24L01
CG023AIR13CG023YD829NRF24L01XN297
CoronaAIR/SFC37COR_V1COR_V2FD_V3CC2500
CX10AIR12GREENBLUEDM007-J3015_1J3015_2MK33041NRF24L01XN297
DevoAIR/SFC7Devo8CH10CH12CH6CH7CHCYRF6936
DM002AIR33NRF24L01XN297
DSMAIR/SFC6DSM2_1FDSM2_2FDSMX_1FDSMX_2FAUTODSMR_1FDSM2SFCCYRF6936
DSM_RXAIR/SFC70MultiCPPMCYRF6936
E010R5AIR81CYRF6936RF2500
E016H85NRF24L01XN297
E016HV280CC2500/NRF24L01unknown
E01X45E012E015CYRF6936HS6200
E12983E129C186CYRF6936RF2500
EazyRC61NRF24L01XN297L
ESky16ESkyET4NRF24L01
ESky15035NRF24L01
ESky150V269CC2500NRF51822
Flysky1FlyskyV9x9V6x6V912CX20A7105
Flysky AFHDS2A28PWM_IBUSPPM_IBUSPWM_SBUSPPM_SBUSGyro_OffGyro_OnGyro_On_RevA7105
Flysky AFHDS2A RX56MultiCPPMA7105
FQ77723124XBM37NRF24L01SSV7241
FrskyD3D8ClonedCC2500
FrskyL67LR12LR12 6CHCC2500
FrskyR965FrskyR9R9_915R9_868SX1276
FrskyV25CC2500
FrskyX15CH_16CH_8EU_16EU_8ClonedCloned_8CC2500
FrskyX264CH_16CH_8EU_16EU_8ClonedCloned_8CC2500
Frsky_RX55MultiCloneTXEraseTXCPPMCC2500
Futaba/SFHSS21SFHSSCC2500
FX58FX816FX6209630Q560QF012BM26A570NRF24L01
FY32620FY326FY319NRF24L01
GD00X47GD_V1*GD_V2*NRF24L01XN297L
GW00832NRF24L01XN297
H36H36NRF24L01XN297
H8_3D36H8_3DH20HH20MiniH30MiniNRF24L01XN297
Height535ch8chA7105
Hisky4HiskyHK310NRF24L01
Hitec39OPT_FWOPT_HUBMINIMACC2500
Hontai26HONTAIJJRCX1X5C1FQ777_951XKK170NRF24L01XN297
HoTT57SyncNo_SyncCC2500
Hubsan2H107H301H501A7105
J6Pro22CYRF6936
JIABAILE102StdGyroNRF24L01XN297
JJRC34571JJRC345SkyTmblrNRF24L01XN297
JOYSWAY84NRF24L01XN297
KAMTOM104NRF24L01XN297
KF60649KF606MIG320ZCZ50NRF24L01XN297
KN9WLTOYSFEILUNNRF24L01
Kyosho73FHSSHypeA7105
Kyosho293KT-17NRF24L01
Kyosho398ASFCYRF6936
LOLI82NRF24L01
Losi89CYRF6936
MJXq18WLH08X600X800H26DE010*H26WHPHOENIX*NRF24L01XN297
MLINK78CYRF6936
MouldKg90A4444D4444A664NRF24L01XN297
MT99xx17MTH7YZLSFY805A180DRAGONF949GNRF24L01XN297
MT99xx292PA18SU35NRF24L01XN297
NCC170144NRF24L01
OMP77CC2500&NRF24L01XN297L
OpenLRS27None
Pelikan60ProLiteSCX24A7105
Potensic51A20NRF24L01XN297
PROPEL6674-ZNRF24L01
Q2X229Q222Q242Q282NRF24L01
Q30331Q303CX35CX10DCX10WDNRF24L01XN297
Q90C72Q90C*NRF24L01XN297
RadioLink74SurfaceAirDumboRCRC4GDumbo_PCC2500
Realacc76R11NRF24L01
Redpine50FASTSLOWNRF24L01XN297
Scanner54CC2500
Scorpio94CYRF6936
SGF2297F22F22SJ20CX10NRF24L01XN297
Shenqi19ShenqiNRF24L01LT8900
Shenqi2105Shenqi2NRF24L01XN297
Skyartec68CC2500CC2500
SLT11SLT_V1SLT_V2Q100Q200MR100V1_4CHRF_SIMNRF24L01CC2500
SymaX10SYMAXSYMAX5CNRF24L01
Traxxas43TQ2TQ1CYRF6936
V2x25V2x2JXD506MR101NRF24L01
V761483CH4CHTOPRCNRF24L01XN297
V911S46V911S*E119*NRF24L01XN297
WFLY40WFR0xCYRF6936
WFLY279RF20xA7105
WK2x0130WK2801WK2401W6_5_1W6_6_1W6_HELW6_HEL_ICYRF6936
WL91X106NRF24L01&CC2500XN297
WPL107NRF24L01XN297
XERALL91TankNRF24L01XN297
XK62X450X420CarsNRF24L01&CC2500XN297
XK299X4P10NRF24L01&CC2500XN297
YD7178YD717SKYWLKRSYMAX4XINXUNNIHUINRF24L01
YuXiang100NRF24L01XN297
ZSX52280NRF24L01XN297
  • "*" Sub Protocols designated by * suffix are using a XN297L@250kbps which will be emulated by default with the NRF24L01. If option (freq tune) is diffrent from 0, the CC2500 module (if installed) will be used instead. Each specific sub protocol has a more detailed explanation.

A7105 RF Module

If USE_A7105_CH15_TUNING is enabled, the value of channel 15 is used by all A7105 protocols for tuning the frequency. This is required in rare cases where some A7105 modules and/or RXs have an inaccurate crystal oscillator.

BUGS - 41

Models: MJX Bugs 3, 6 and 8

Telemetry enabled for RX & TX RSSI, Battery voltage good/bad

RX_Num is used to give a number to a given model. You must use a different RX_Num per MJX Bugs. A maximum of 16 Bugs are supported.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRARMANGLEFLIPPICTUREVIDEOLED

ANGLE: angle is +100%, acro is -100%

FLYSKY - 1

Extended limits supported

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

RX output will match the Flysky standard AETR independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.

Sub_protocol Flysky - 0

Supports a variety of Flysky receivers and integrated boards.

Kyosho FHS MINI-Z also uses this protocol with this channel assignement:

CH1CH2CH3CH4CH5
SteeringThrottleLightsSteering travelOthers:not sure

Sub_protocol V9X9 - 1

CH5CH6CH7CH8
FLIPLIGHTPICTUREVIDEO

Sub_protocol V6X6 - 2

CH5CH6CH7CH8CH9CH10CH11CH12
FLIPLIGHTPICTUREVIDEOHEADLESSRTHXCALYCAL

Sub_protocol V912 - 3

CH5CH6
BTMBTNTOPBTN

Sub_protocol CX20 - 4

Model: Cheerson Cx-20

CH5CH6CH7

FLYSKY AFHDS2A - 28

Extended limits and failsafe supported

Telemetry enabled protocol:

  • by defaut using FrSky Hub protocol (for example er9x): A1=RX voltage (set the ratio to 12.7 and adjust with offset), A2=battery voltage FS-CVT01 (set the ratio to 12.7 and adjust with offset) and RX&TX RSSI
  • if using erskyTX and OpenTX: full telemetry information available
  • if telemetry is incomplete (missing RX RSSI for example), it means that you have to upgrade your RX firmware to version 1.6 or later. You can do it from an original Flysky TX or using a STLink like explained in this tutorial.

LQI: Link Quality Indicator which is sent back to the RX on CH17

Option is used to change the servo refresh rate. A value of 0 gives 50Hz (min), 70 gives 400Hz (max). Specific refresh rate value can be calculated like this option=(refresh_rate-50)/5.

RX_Num is used to give a number a given RX. You must use a different RX_Num per RX. A maximum of 64 AFHDS2A RXs are supported.

Sub_protocol PWM_IBUS - 0

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
AETRCH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16LQI

RX output will match the Flysky standard AETR.

Sub_protocol PPM_IBUS - 1

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
AETRCH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16LQI

RX output will match the Flysky standard AETR.

Sub_protocol PWM_SBUS - 2

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
AETRCH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16LQI

RX output will match the Flysky standard AETR.

Sub_protocol Gyro_Off - 3

RXs: FS-BS6, FS-BS4

Gyro is off

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12----LQI

Sub_protocol Gyro_On - 4

RXs: FS-BS6, FS-BS4

Gyro is on

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12ST_GainTH_GainPriorityCalibLQI

Sub_protocol Gyro_On_Rev - 5

RXs: FS-BS6, FS-BS4

Gyro is on and reversed

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16CH17
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12ST_GainTH_GainPriorityCalibLQI

FLYSKY AFHDS2A RX - 56

The Flysky AFHDS2A receiver protocol enables master/slave trainning, separate access from 2 different radios to the same model,...

Available in OpenTX 2.3.3, Trainer Mode Master/Multi

Extended limits supported

Low power: enable/disable the LNA stage on the RF component to use depending on the distance with the TX.

Sub_protocol Multi - 0

Use the telemetry to send the trainer information to the radio. Available in OpenTX 2.3.3, Trainer Mode Master/Multi

Sub_protocol CPPM - 1

Sending trainer channels to FrSky radios through telemetry does not work since the telemetry lines of the internal and external modules are shared (hardware limitation). On a STM32 module and with a simple hardware modification, you can go around this limitation using CPPM to send the trainer information to the radio. For more information check the CCPM Hardware Modification page.

Once your setup is complete and before enabling the internal module, you must check the "Disable Telemetry" box to stop the Multi module from sending any data to the radio and therfore freeing up the line for the internal module.

HEIGHT - 53

Sub_protocol 5CH - 0

Models from Height, Flyzone, Rage R/C, eRC and the old ARES (prior to Hitec RED).

CH1CH2CH3CH4CH5
AETRGear

Sub_protocol 8CH - 1

Models from Height and Rage R/C.

CH1CH2CH3CH4CH5CH6CH7CH8
AETRGearGyroFlapLight

HUBSAN - 2

Telemetry enabled for A1=battery voltage (set the ratio to 12.7 and adjust with offset) and TX RSSI

Option=vTX frequency (H107D) 5645 - 5900 MHz

Sub_protocol H107 - 0

Autobind protocol

Models: Hubsan H102D, H107/L/C/D and H107P/C+/D+

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPLIGHTPICTUREVIDEOHEADLESS

Sub_protocol H301 - 1

Models: Hubsan H301

CH1CH2CH3CH4CH5CH6CH7CH8
AETRRTHLIGHTSTABVIDEO

Sub_protocol H501 - 2

Models: Hubsan H501S, H122D, H123D

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRRTHLIGHTPICTUREVIDEOHEADLESSGPS_HOLDALT_HOLDFLIPFMODES

H122D: FLIP

H123D: FMODES -> -100%=Sport mode 1,0%=Sport mode 2,+100%=Acro

JOYSWAY - 84

CH1CH2CH3CH4
CH1CH2CH3CH4

Kyosho - 73

Sub_protocol FHSS - 0

Surface protocol called FHSS introduced in 2017. Transmitter: KT-531P. Models: Mini-Z.

Surface protocol called Syncro. TX: KT-331, RX: KR-331

Extended limits supported

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14
STEERINGTHROTTLECH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14

Sub_protocol Hype - 1

Transmitters: ST6DF, HK6S, Flightsport. Receivers: ST6DF, HK6DF.

CH1CH2CH3CH4CH5CH6
AETRCH5CH6

RX output will match the Hype standard AETR independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.

Pelikan - 60

Extended limits supported

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

RX output will match the Pelikan standard AETR independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.

Sub_protocol Pro - 0

Models: TX: CADET PRO V4, RX: RX-602 V4

Sub_protocol Lite - 1

Models: TX: CADET 4 LITE

Only 1 frequency hopping table

Sub_protocol SCX24 - 2

TX: Axial AX-4 2.4GHz transmitter, HPI TF-41 and Panda Hobby 3CH Smart Radio 2.4GHz (MT-305A)

Models: Axial SCX24: Deadbolt, Jeep Wranger Rubicon, Chevrolet 1967 C10, B-17 Betty, HPI RF-50 and Panda Hobby: Tetra K1, X1, X2

Extended limits supported

CH1CH2CH3
STEERINGTHROTTLECH3

WFLY2 - 79

Receivers: RF201S,RF206S,RF207S,RF209S

Extended limits supported

Failsafe fully supported (value, hold and no pulse).

Telemetry enabled for A1=RX_Batt (Ratio 12.7), A2=Ext_Batt (Ratio 12.7), RX RSSI, TX RSSI, TX LQI (100=all telem packets received...0=no telem packets).

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10

Option is used to select between WBUS=0 and PPM=1


CYRF6936 RF Module

If USE_CYRF6936_CH15_TUNING is enabled, the value of channel 15 is used by all CYRF6936 protocols for tuning the frequency. This is required in rare cases where some CYRF6936 modules and/or RXs have an inaccurate crystal oscillator.

DEVO - 7

Extended limits and failsafe supported

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRCH5CH6CH7CH8CH9CH10CH11CH12

RX output will match the Devo standard EATR independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.

Full telemetry is available if the RX supports it: TX_RSSI, A1 (set the ratio to 12.7) and A2 (set the ratio to 12.7), VFAS, RPM, temperature 1&2, GPS position/speed/altitude/time. The GPS coordinates come in two flavors which can't be distinguished programmatically, to switch from one to the other add 2 to the Option/FixedID setting value (0->2, 1->3).

Bind procedure using serial:

  • With the TX off, put the binding plug in and power on the RX (RX LED slow blink), then power it down and remove the binding plug. Receiver should now be in autobind mode.
  • Turn on the TX, set protocol = Devo with Option/FixedID=0, turn off the TX (TX is now in autobind mode).
  • Turn on RX (RX LED fast blink).
  • Turn on TX (RX LED solid, TX LED fast blink).
  • Wait for bind on the TX to complete (TX LED solid).
  • Make sure to set a uniq RX_Num value for model match.
  • Change Option/FixedID to 1 to use the global ID.
  • Do not touch Option/FixedID and RX_Num anymore.
  • Note: it might be limited to only the RX705 but to get telemetry, the Option/FixedID field has to be set back to 0 at then end of the procedure...

Bind procedure using PPM:

  • With the TX off, put the binding plug in and power on the RX (RX LED slow blink), then power it down and remove the binding plug. Receiver should now be in autobind mode.
  • Turn on RX (RX LED fast blink).
  • Turn the dial to the model number running protocol DEVO on the module.
  • Press the bind button and turn on the TX. TX is now in autobind mode.
  • Release bind button after 1 second: RX LED solid, TX LED fast blink.
  • Wait for bind on the TX to complete (TX LED solid).
  • Press the bind button for 1 second. TX/RX is now in fixed ID mode.
  • To verify that the TX is in fixed mode: power cycle the TX, the module LED should be solid ON (no blink).
  • Note: Autobind/fixed ID mode is linked to the RX_Num number. Which means that you can have multiple dial numbers set to the same protocol DEVO with different RX_Num and have different bind modes at the same time. It enables PPM users to get model match under DEVO.

Sub_protocol 8CH - 0

Sub_protocol 10CH - 1

Sub_protocol 12CH - 2

Sub_protocol 6CH - 3

Sub_protocol 7CH - 4

WK2X01 - 30

Extended limits supported Autobind protocol

Note: RX ouput will always be AETR independently of the input AETR, RETA...

Sub_protocol WK2801 - 0

Failsafe supported.

This roughly corresponds to the number of channels supported, but many of the newer 6-channel receivers actually support the WK2801 protocol. It is recommended to try the WK2801 protocol 1st when working with older Walkera models before attempting the WK2601 or WK2401 mode, as the WK2801 is a superior protocol. The WK2801 protocol supports up to 8 channels.

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

Bind procedure using serial:

  • With the TX off, put the binding plug in and power on the RX (RX LED slow blink), then power it down and remove the binding plug. Receiver should now be in autobind mode.
  • Turn on the TX, set protocol = WK2X01, sub_protocol = WK2801 with option=0, turn off the TX (TX is now in autobind mode).
  • Turn on RX (RX LED fast blink).
  • Turn on TX (RX LED solid, TX LED fast blink).
  • Wait for bind on the TX to complete (TX LED solid).
  • Make sure to set a uniq RX_Num value for model match.
  • Change option to 1 to use the global ID.
  • Do not touch option/RX_Num anymore.

Bind procedure using PPM:

  • With the TX off, put the binding plug in and power on the RX (RX LED slow blink), then power it down and remove the binding plug. Receiver should now be in autobind mode.
  • Turn on RX (RX LED fast blink).
  • Turn the dial to the model number running protocol protocol WK2X01 and sub_protocol WK2801 on the module.
  • Press the bind button and turn on the TX. TX is now in autobind mode.
  • Release bind button after 1 second: RX LED solid, TX LED fast blink.
  • Wait for bind on the TX to complete (TX LED solid).
  • Press the bind button for 1 second. TX/RX is now in fixed ID mode.
  • To verify that the TX is in fixed mode: power cycle the TX, the module LED should be solid ON (no blink).
  • Note: Autobind/fixed ID mode is linked to the RX_Num number. Which means that you can have multiple dial numbers set to the same protocol DEVO with different RX_Num and have different bind modes at the same time. It enables PPM users to get model match under DEVO.

Sub_protocol WK2401 - 1

The WK2401 protocol is used to control older Walkera models.

CH1CH2CH3CH4
AETR

Sub_protocol W6_5_1 - 2

WK2601 5+1: AIL, ELE, THR, RUD, GYRO (ch 7) are proportional. Gear (ch 5) is binary. Ch 6 is disabled

CH1CH2CH3CH4CH5CH6CH7
AETRGEARDISGYRO

Sub_protocol W6_6_1 - 3

WK2601 6+1: AIL, ELE, THR, RUD, COL (ch 6), GYRO (ch 7) are proportional. Gear (ch 5) is binary. This mode is highly experimental.

CH1CH2CH3CH4CH5CH6CH7
AETRGEARCOLGYRO

Sub_protocol W6_HEL - 4 and W6HEL_I - 5

WK2601 Heli: AIL, ELE, THR, RUD, GYRO are proportional. Gear (ch 5) is binary. COL (ch 6) is linked to Thr. If Ch6 >= 0, the receiver will apply a 3D curve to the Thr. If Ch6 < 0, the receiver will apply normal curves to the Thr. The value of Ch6 defines the ratio of COL to THR.

W6HEL_I: Invert COL servo

option= maximum range of COL servo

CH1CH2CH3CH4CH5CH6CH7
AETRGEARCOLGYRO

DSM - 6

Extended limits supported

Telemetry enabled for TSSI and plugins

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12----CH14
AETRCH5CH6CH7CH8CH9CH10CH11CH12----TH_KILL

Notes:

  • The "AUTO" sub protocol is recommended to automatically select the best settings for your DSM RX. If the RX doesn't bind or work properly after bind, don't hesitate to test different combinations of sub protocol and number of channels until you have something working.
  • Servo refresh rate is 22ms unless you select 11ms available in OpenTX 2.3.10+
  • RX output will match the Spektrum standard TAER independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.
  • RX output will match the Spektrum standard throw (1500µs +/- 400µs -> 1100..1900µs) for a 100% input. This is true for both Serial and PPM input. For PPM, make sure the end points PPM_MIN_100 and PPM_MAX_100 in _config.h are matching your TX ouput. The maximum ouput is 1000..2000µs based on an input of 125%.
    • If you want to override the above and get maximum throw either uncomment in _config.h the line #define DSM_MAX_THROW or on OpenTX 2.3.3+ use the "Enable max throw" feature on the GUI (0=No,1=Yes). In this mode to achieve standard throw use a channel weight of 84%.
  • TH_KILL is a feature which is enabled on channel 14 by default (can be disabled/changed) in the _config.h file. Some models (X-Vert, Blade 230S...) require a special position to instant stop the motor(s). If the channel 14 is above -50% the throttle is untouched but if it is between -50% and -100%, the throttle output will be forced between -100% and -150%. For example, a value of -80% applied on channel 14 will instantly kill the motors on the X-Vert.
  • To allow SAFE to be ON with a switch assignment you must remove the bind plug after powering up the RX but before turning on the TX to bind. If you select Autodetect to bind, The MPM will choose DSMX 11ms and Channels 1-7 ( Change to 1-9 if you wish to assign switch above channel 7 ). Then in order to use the manuals diagram of both sticks "Down-Inside" to set a SAFE Select Switch Designation, you must have Throttle and Elevator channels set to Normal direction but the Aileron and Rudder set to Reverse direction. If setting up a new model with all channels set to Normal you can hold both sticks "Down- OUTSIDE" to assign the switch with 5x flips. Tested on a Mode2 radio.

Option=number of channels from 3 to 12. Option|0x80 enables Max Throw. Option|0x40 enables a servo refresh rate of 11ms.

Here is a table detailling the different RX output ranges based on the radio settings: Image

Sub_protocol DSM2_1F - 0

Air DSM2, Resolution 1024, servo refresh rate can only be 22ms

Sub_protocol DSM2_2F - 1

Air DSM2, Resolution 2048, servo refresh rate can be 22 or 11ms. 11ms won't be available on all servo outputs when more than 7 channels are used.

Sub_protocol DSMX_1F - 2

Air DSMX, Resolution 2048, servo refresh rate can only be 22ms

Sub_protocol DSMX_2F - 3

Air DSMX, Resolution 2048, servo refresh rate can be 22 or 11ms. 11ms won't be available on all servo outputs when more than 7 channels are used.

Sub_protocol AUTO - 4

"AUTO" is recommended to automatically select the best settings for your air DSM2 and DSMX RXs.

Sub_protocol DSMR_1F - 5

Surface DSMR receivers

Only 22 IDs available, use RX num to cycle through them.

Telemetry enabled, extended limits available and no channel mapping. Do not use DSM/AUTO to bind but DSM/R_1F instead.

CH1CH2CH3CH4CH5CH6CH7
STRTHRAUX1AUX2AUX3AUX4AUX5

Sub_protocol DSM2SFC - 6

Surface DSM2 receivers, tested with a SR3100

Extended limits available and no channel mapping. Do not use DSM/AUTO to bind but DSM/2SFC instead.

Servo refresh rate 22/11ms is repurposed to the frame rates 16.5ms(22) and 11ms(11).

CH1CH2CH3
STRTHRAUX1

DSM_RX - 70

The DSM receiver protocol enables master/slave trainning, separate access from 2 different radios to the same model,...

Notes:

  • Automatically detect DSM 2/X 11/22ms 1024/2048res
  • Bind should be done with all other modules off in the radio
  • Available in OpenTX 2.3.3+, Trainer Mode Master/Multi
  • Channels 1..4 are remapped to the module default channel order unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.
  • Extended limits supported
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRCH5CH6CH7CH8CH9CH10CH11CH12

Sub_protocol Multi - 0

Use the telemetry to send the trainer information to the radio.

Sub_protocol CPPM - 1

Sending trainer channels to FrSky radios through telemetry does not work since the telemetry lines of the internal and external modules are shared (hardware limitation). On a STM32 module and with a simple hardware modification, you can go around this limitation using CPPM to send the trainer information to the radio. For more information check the CCPM Hardware Modification page.

Once your setup is complete and before enabling the internal module, you must check the "Disable Telemetry" box to stop the Multi module from sending any data to the radio and therfore freeing up the line for the internal module.

E010R5 - 81

Models: E010 R5 red boards, JJRC H36, H36F and H36S

Not supported by Atmega328p modules.

Autobind protocol.

Only 5 IDs are available. Use RX num to cycle through them. More IDs can be added if you send me your "unused" original TX.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRFLIPLEDCALIBHEADLESSRTHGLIDE

E01X - 45

Autobind protocol

Not supported by Atmega328p modules.

Sub_protocol E012 - 0

Models: Eachine E012

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPHEADLESSRTH

Sub_protocol E015 - 1

Models: Eachine E015

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRARMFLIPLEDHEADLESSRTH

E129 - 83

Not supported by Atmega328p modules.

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRTake off/LandEmergencyTrim ATrim ETrim R

Trims can be done to some extent on the AETR channels directly but if you push them too far you won't be able to arm like explained below. In this case use the associated trim TrimA/E/R instead.

Take off with a none spring throttle is easier by putting both sticks down outwards (like on the original radio) in Mode 1/2, not sure about other modes.

Calib is the same as the original radio with both sticks down and to the left in Mode 1/2, not sure about other modes.

Sub_protocol E129 - 0

Models: Eachine E129/E130 and Twister Ninja 250

Sub_protocol C186 - 1

Models: RC ERA C186/E120, C127/E110, K127, C159, C189, C129v2

The FC of the heli store the trims Trim A/E/R=CH7..9. If you use these trims, make sure to reset them to 0 after powering off the heli or they will be added to the previous trims therefore over correctting.

CH10CH11CH12
LoopFlipDebug

Loop: circular flight on the C159 (others?)

Flip: flip/aerobatic on the C129v2 (others?)

Debug: you must know what you are doing!!! The new values are stored at power off. The rudder trim is used to change the pitch value (relative to the previously stored value). Ail end Ele trims are used to better trim the FC.

J6Pro - 22

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRCH5CH6CH7CH8CH9CH10CH11CH12

Kyosho3 - 98

Sub_protocol ASF - 0

Surface protocol ASF. Models: Mini-Z.

Extended limits supported

CH1CH2CH3CH4
STEERINGTHROTTLECH3CH4

Losi - 89

TX: LSR-3000

Extended limits supported

CH1CH2CH3
STTHRCH3

Extended limits supported

Bind: the RX must be really close to the TX

Failsafe MUST be configured once with the desired channel values (hold or no pulses are not supported) while the RX is up (wait 10+sec for the RX to learn the config) and then failsafe MUST be set to RX/Receiver otherwise the servos will jitter!!!

Telemetry: the 2 RXs I have are sending different information in different format

  • RX-5: RX_RSSI=RSSI=sort of RSSI or link quality, RX_LQI=number of connection lost, TX_RSSI=RSSI from the TX perspective, TX_LQI=percentage of received telemetry packets
  • RX-9-DR: A1=RX Batt (Ratio=12.7), RX_RSSI=TX_LQI=percentage of received telemetry packets from the TX perspective not RX, TX_RSSI=RSSI from the TX perspective, TX_LQI=percentage of received telemetry packets
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Scorpio - 94

Model Scorpio Falco 300, TX:Nine Eagles 4CH-TX, RX:Nine Eagles 4CH-RX

CH1CH2CH3CH4
AETR

Traxxas - 43

You must assign a different RX number for each receiver/car. Otherwise the new receiver/car ID will overwrite the previous one.

Sub_protocol TQ2 - 0

Transmitter TQ, Receivers: 6519, 2218(X), ECM-2.5

Extended limits supported

CH1CH2CH3CH4CH5CH6
CH1CH2CH3CH4CH5CH6

Warning from v1.3.4.7 channels order have changed

Sub_protocol TQ1 - 1

Transmitter 2228 TX and a 2217 RX

WFLY - 40

Receivers: WFR04S, WFR07S, WFR09S

Extended limits supported

Failsafe values supported (not hold or none)

Option=number of channels from 4 to 9. An invalid option value will end up sending 9 channels.

CH1CH2CH3CH4CH5CH6CH7CH8CH9
CH1CH2CH3CH4CH5CH6CH7CH8CH9

CC2500 RF Module

CORONA - 37

Models: Corona 2.4GHz FSS and DSSS receivers.

Extended limits supported

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol COR_V1 - 0

Corona FSS V1 RXs

Sub_protocol COR_V2 - 1

Corona DSSS V2 RXs: CR8D, CR6D and CR4D

To bind V2 RXs you must follow the below procedure (original):

  • press the bind button and power on the RX
  • launch a bind from Multi -> the RX will blink 2 times
  • turn off the RX and TX(=Multi)
  • turn on the RX first
  • turn on the TX(=Multi) second
  • wait for the bind to complete -> the RX will flash, stop and finally fix
  • wait some time (more than 30 sec) before turning off the RX
  • turn off/on the RX and test that it can reconnect instantly, if not repeat the bind procedure

Sub_protocol FD_V3 - 2

FlyDream RXs like IS-4R and IS-4R0

E016HV2 - 80

Models: E016H v2

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable or bind won't even work. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRTAKE_OFF/LANDINGEMERGENCYFLIPCALIBHEADLESSRTH

TAKE_OFF/LANDING: this is a momentary switch to arm the motors or land the quad. This switch is not really needed as you can start the quad with throttle low then increase throttle until the motor arms, move throttle to mid-stick and then increase it quickly to lift off; To land just bring throttle all the way down, the quad will just stops when touching the ground.

EMERGENCY: Can be used along with the throttle cut switch: Throttle cut=set throttle at -100% and set EMERGENCY to 100%

ESKY150V2 - 69

ESky protocol for small models: 150 V2, F150 V2, Blade 70s

Notes:

  • RX output will match the eSky standard TAER independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.
  • To run this protocol you need both CC2500 and NRF24L01 to be enabled for code reasons, only the CC2500 is really used.
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
AETRCH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

RATE for the F150 V2 is assigned to channel 5: -100%=low, 100%=high

FRSKYV - 25

Models: FrSky receivers V8R4, V8R7 and V8FR.

  • FrSkyV = FrSky 1 way

Extended limits supported

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4
CH1CH2CH3CH4

FRSKYD - 3

Models: FrSky receivers D4R and D8R. DIY RX-F801 and RX-F802 receivers. Also known as D8.

Extended limits supported

Telemetry enabled for A0, A1, RSSI, TX_RSSI, TX_LQI and Hub. Lowest the TX_LQI value is best the quality link is, it's a good indicator of how well the module is tuned.

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol D8 - 0

Use the internal multi module Identifier.

Sub_protocol Cloned - 1

Use the identifier learnt from another FrSky radio when binding with the FrSkyRX/CloneTX mode.

RX number can't be used anymore and is ignored.

FRSKYL - 67

Models: FrSky receivers L9R. Also known as LR12.

Extended limits supported

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

Sub_protocol LR12 - 0

Refresh rate: 36ms

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12

Sub_protocol LR12 6ch - 1

Refresh rate: 18ms

CH1CH2CH3CH4CH5CH6
CH1CH2CH3CH4CH5CH6

FRSKYX - 15

Models: FrSky v1.xxx receivers X4R, X6R and X8R. Protocol also known as D16 v1 FCC/LBT.

Extended limits and failsafe supported

Telemetry enabled for A1 (RxBatt), A2, RSSI, TX_RSSI, TX_LQI and Hub. Lowest the TX_LQI value is best the quality link is, it's a good indicator of how well the module is tuned.

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

Sub_protocol CH_16 - 0

FCC protocol 16 channels @18ms.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol CH_8 - 1

FCC protocol 8 channels @9ms.

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol EU_16 - 2

EU-LBT protocol 16 channels @18ms.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol EU_8 - 3

EU-LBT protocol 8 channels @9ms.

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol Cloned - 4

Use the identifier learnt from another FrSky radio when binding with the FrSkyRX/CloneTX mode.

16 channels.

Sub_protocol Cloned_8 - 5

Use the identifier learnt from another FrSky radio when binding with the FrSkyRX/CloneTX mode.

8 channels.

FRSKYX2 - 64

Same as FrskyX but for D16 v2.1.0 FCC/LBT.

FRSKY_RX - 55

Sub_protocol Multi - 0

The FrSky receiver protocol enables master/slave trainning, separate access from 2 different radios to the same model,...

Auto detection of the protocol used by a TX transmitting FrSkyD/D8, FrSkyX/D16 v1.xxx FCC/LBT or FrSkyX/D16 v2.1.0 FCC/LBT at bind time.

Available in OpenTX 2.3.3, Trainer Mode Master/Multi

Extended limits supported

For FrSkyX, RX num must match on the master and slave. This enables a multi student configuration for example.

Option for this protocol corresponds to fine frequency tuning. If the value is equal to 0, the RX will auto tune otherwise it will use the indicated value. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

Low power: enable/disable the LNA stage on the RF component to use depending on the distance with the TX.

Sub_protocol CPPM - 3

Sending trainer channels to FrSky radios through telemetry does not work since the telemetry lines of the internal and external modules are shared (hardware limitation). On a STM32 module and with a simple hardware modification, you can go around this limitation using CPPM to send the trainer information to the radio. For more information check the CCPM Hardware Modification page.

Once your setup is complete and before enabling the internal module, you must check the "Disable Telemetry" box to stop the Multi module from sending any data to the radio and therfore freeing up the line for the internal module.

Sub_protocol CloneTX - 1

This subprotocol makes a clone of a TX identifier transmitting FrSkyD/D8, FrSkyX/D16 v1.xxx FCC/LBT and FrSkyX/D16 v2.1.0 FCC/LBT.

There are 3 slots available, 1 slot for D8 cloning, 1 slot for FrSkyX (D16v1) cloning and 1 slot for FrSkyX2 (D16v2.1.0) cloning. The same TX or different TXs can be used for each slot but a maximum of 1 per slot. If you launch the FrSky_RX/CloneTX protocol and do a bind with a TX transmitting with the D8 protocol, it will be saved in the slot D8. Same for D16v1 and D16v2.1 . Then the system will alow you to enable cloning as you wish for each model using the FrSkyD/X/X2 "Cloned" subprotocol. This way you can have models working with the original MPM indentifier and models which are shared by both the cloned TX and MPM.

Clone mode operation:

  • Select the FrSky_RX protocol, subprotocol CloneTX
  • Select on the TX to be cloned the protocol you want to clone the identifier from: FrSkyD/D8 or FrSkyX/D16 v1.xxx FCC/LBT or FrSkyX/D16 v2.1.0 FCC/LBT
  • Place both the TX and MPM in bind mode
  • Wait for the bind to complete
  • To use the cloned TX identifier, open a new model select the protocol you just cloned/binded and select the subprotocol "Cloned"

Notes:

  • OpenTX 2.3.8 N184 (nightly) or later is needed to have access to the "D8Cloned" and "D16Cloned" subprotocols, D16v2.1 "Cloned" is available under FrSkyX2/Cloned.
  • For FrSkyD, only the RX number used during bind is cloned -> you can't use RX num anymore
  • For FrSkyX and FrSkyX2, RX number has to be adjusted on each model to match the original TX model

Sub_protocol EraseTX - 2

This subprotocol erases ALL the clone IDs which have been recorded.

To erase ALL the clone information, select the sub_protocol EraseTX and execute a bind.

HITEC - 39

Models: OPTIMA, MINIMA and MICRO receivers.

Extended limits supported

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8CH9
CH1CH2CH3CH4CH5CH6CH7CH8CH9

Sub_protocol OPT_FW - 0

OPTIMA RXs

Full telemetry available on OpenTX 2.3.3+, still in progress for erskyTx. Lowest the TX_LQI value is best the quality link is, it's a good indicator of how well the module is tuned.

The TX must be close to the RX for the bind negotiation to complete successfully

Sub_protocol OPT_HUB - 1

OPTIMA RXs

Basic telemetry using FrSky Hub on er9x, erskyTX, OpenTX and any radio with FrSky telemetry support with RX voltage, VOLT2 voltage, TX_RSSI and TX_LQI. Lowest the TX_LQI value is best the quality link is, it's a good indicator of how well the module is tuned.

The TX must be close to the RX for the bind negotiation to complete successfully

Sub_protocol MINIMA - 2

MINIMA, MICRO and RED receivers. Also used by ARES planes.

HoTT - 57

Models: Graupner HoTT receivers (tested on GR-12, GR-12L, GR-16, GR-32 and Vector).

Extended limits, failsafe and LBT supported.

Full telemetry and full text config mode are available starting from OpenTX 2.3.8N226.

RX_Num is used to give a number to a given RX. You must use a different RX_Num per RX. A maximum of 64 HoTT RXs are supported.

Failsafe MUST be configured once with the desired channel values (hold or position) while the RX is up (wait 10+sec for the RX to learn the config) and then failsafe MUST be set to RX/Receiver otherwise the servos will jitter!!!

The RX and sensors/FC features configuration are done through the OpenTX script "Graupner HoTT.lua".

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol Sync - 0

Recommended for best telemetry performance.

Sub_protocol No_Sync - 1

Telemetry compatibility mode when Sync does not work due to an old firmware on the RX. You should definitively upgrade your receivers/sensors to the latest firmware versions: https://www.rcgroups.com/forums/showpost.php?p=44668015&postcount=18022

Scanner - 54

2.4GHz scanner accessible using the OpenTX 2.3 Spectrum Analyser tool.

Extended limits

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8FS_CH1FS_CH2FS_CH3FS_CH4FS_CH5FS_CH6FS_CH7FS_CH8

FS=FailSafe

Sub_protocol Surface - 0

Surface protocol. TXs: RC4GS,RC6GS. Compatible RXs: R7FG(Std),R6FG,R6F,R8EF,R8FM,R8F,R4FGM,R4F

CH1=Steering, CH2=Throttle, CH8=Gyro gain

Telemetry: RX_RSSI (for the original value add -256), TX_RSSI, TX_QLY (0..100%), A1=RX_Batt (set the ratio to 12.7 and adjust with offset), A2=Batt (set the ratio to 25.5 and adjust with offset)

Sub_protocol Air - 1

Air protocol. TXs: T8FB,T8S. Compatible RXs: R8EF,R8FM,R8SM,R4FG,R4F

Telemetry: RX_RSSI (for the original value add -256), TX_RSSI, TX_QLY (0..100%)

Sub_protocol DumboRC - 2

Compatible RXs:

  • X6/X6F/X6FG/X6DC/X6DCG/X10F/X10FG (Other X Series should work as well)
  • P6F/P6FG/P6DC/P6DCG/P6FP/P10F/P10FG (Other P Series should work as well)

For P series specific features, see subprotocol 4 below.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
CH1CH2CH3CH4CH5CH6CH7CH8/Gyro gainCH9CH10

Telemetry:

  • RX_RSSI uses the receiver's direct percentage when available
  • TX_RSSI is the module-side received RSSI
  • TX_QLY is 0..100%
  • A2=external battery voltage in 0.1V units (set the ratio to 25.5 and adjust with offset)

Sub_protocol RC4G - 3

Compatible RXs: R4EH-G(/R4EH-H)

CH1CH2CH3CH4CH5CH6CH7CH8CH9
CH1CH2CH3CH4CH5FS_CH1FS_CH2FS_CH3FS_CH4

FS=FailSafe

CH5 is driven by CH3 on the original TX, gyro sensitivity?

Sub_protocol Dumbo_P - 4

Compatible RXs: P6F/P6FG/P6DC/P6DCG/P6FP/P10F/P10FG (Other P Series should work as well)

P series supports configuring receiver from transmitter. Originally, this logic appeared on DumboRC DDF-350 transmitter in 1.1.5 firmware version.

You can adjust these settings by using "DumboRC P Series.lua" script.

Settings include:

  • gyro on/off
  • gyro phase
  • gyro tuning
  • gyro gain channel
  • setting gyro endpoints
  • setting failsafe values

Futaba - 21

Also called SFHSS depending on radio version.

Sub_protocol SFHSS - 0

Models: Futaba SFHSS RXs and some XK models.

Extended limits and failsafe supported.

RX output will match the Futaba standard servo throw, mid point and the channel order AETR independently of the input configuration AETR, RETA... unless if on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI.

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

This protocol does not use bind on the TX side. The RX attaches to the first S-FHHSS TX around it when the bind button is pressed.

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

Skyartec - 68

Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7
AETRCH5CH6CH7

CC2500 and/or NRF24L01 RF Module(s)

If a CC2500 is installed it will be used for all the below protocols. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then these protocols might be problematic because they are using the XN297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

BLUEFLY - 95

Model: HP100

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

TRIM: either use this channel for trim only or add a mixer with aileron to increase the roll rate.

RATE: -100% high rate, +100% low rate

GD00X - 47

Model: GD005 C-17 Transport, GD006 DA62 and ZC-Z50

CH1CH2CH3CH4CH5CH6CH7
ATTRIMLEDRATE

TRIM: either use this channel for trim only or add a mixer with aileron to increase the roll rate.

RATE: -100% high rate, +100% low rate

Sub_protocol GD_V1 - 0

First generation of GD models, ZC-Z50

Sub_protocol GD_V2 - 1

New generation of GD models

KF606 - 49

Sub_protocol KF606 - 0

Model: KF606

CH1CH2CH3CH4CH5CH6
ATTRIMLED

Sub_protocol MIG320 - 1

Model: Zhiyang MIG-320

CH1CH2CH3CH4CH5CH6
ATTRIMLED

Sub_protocol ZCZ50v2 - 2

Model: ZC-Z50 Cessna

This might be newer version of the model. My plane does not have front propeller, but its just fake anyway (no motor in the front).

CH1CH2CH3CH4CH5CH6
ATTRIMUNKNOWN

MJXQ - 18

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14
AETRFLIPLEDPICTUREVIDEOHEADLESSRTHAUTOFLIPPANTILTRATE

RATE: -100%(default)=>higher rates by enabling dynamic trims (except for Headless), 100%=>disable dynamic trims

CC2500: only E010 and PHOENIX are supported.

Sub_protocol WLH08 - 0

Sub_protocol X600 - 1

Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them

Sub_protocol X800 - 2

Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them

Sub_protocol H26D - 3

Only 3 TX IDs available, change RX_Num value 0..2 to cycle through them

Sub_protocol E010 - 4

15 TX IDs available, change RX_Num value 0..14 to cycle through them

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

Sub_protocol H26WH - 5

CH6
ARM

Only 1 TX ID available

Sub_protocol PHOENIX - 6

CH6
ARM

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

MT99XX - 17

Autobind protocol

CC2500: only YZ and F949G are supported.

Sub_protocol MT99 - 0

Models: MT99xx

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLEDPICTUREVIDEOHEADLESSATrimETrim

Sub_protocol H7 - 1

Models: Eachine H7, Cheerson CX023

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLEDPICTUREVIDEOHEADLESSATrimETrim

Sub_protocol YZ - 2

Model: Yi Zhan i6S

Only one model can be flown at the same time since the ID is hardcoded.

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLEDPICTUREVIDEOHEADLESSATrimETrim

Sub_protocol LS - 3

Models: LS114, 124, 215

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPINVERTPICTUREVIDEOHEADLESSATrimETrim

Sub_protocol FY805 - 4

Model: FY805

Only 1 ID available

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPHEADLESSATrimETrim

Sub_protocol A180 - 5

Model: XK A180, A120, F949S, F959

A180:

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETR3D6GRATEATrimETrim

A120:

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRRATELEDATrimETrim

F949S:

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRRATERXLED3D6GATrimETrim

Sub_protocol DRAGON - 6

Model: Eachine Mini Wing Dragon, Eachine Mini Cessna

Telemetry is supported: A1 = battery voltage with a Ratio of 25.5, A2=battery low flag (0=off,>0=on) and RSSI = dummy value of 100

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRMODERTHATrimETrim

MODE: -100%=Beginner, 0%=Intermediate, +100%=Advanced

Sub_protocol F949G - 7

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

Model: F949G

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETR6G3DLightATrimETrim

Model: KFPLAN Z-Series like Z61 BF109, Z54 A380,...

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRRateLightUnk1Unk2ATrimETrim

Unk1&2: long press right/left

MT99XX2 - 92

Sub_protocol PA18 - 0

Model: PA18 mini

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRMODEFLIPRTHATrimETrim

MODE: -100% beginner, 0% intermediate, +100% Expert

Sub_protocol SU35 - 1

Model: QF009 SU35

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRMODELEDLED_FLASHINVERTRATEATrimETrim

MODE: -100% 6G, +100% 3D

OMP - 77

Model: OMPHOBBY M1 & M2 Helis, T720 RC Glider

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

Telemetry is supported:

  • A1 = battery voltage including "recovered" battery voltage from corrupted telemetry packets
  • A2 = battery voltage from only good telemetry packets
  • How to calculate accurately the OpenTX Ratio and Offset: Set the Ratio to 12.7 and Offset to 0, plug 2 batteries with extreme voltage values, write down the values Batt1=12.5V & Telem1=12.2V, Batt2=7V & Telem2=6.6V then calculate/set Ratio=12.7*[(12.5-7)/(12.2-6.6)]=12.47 => 12.5 and Offset=12.5-12.2*[(12.5-7)/(12.2-6.6)]=0.517 => 0.5
  • RX_RSSI = TQly = percentage of received telemetry packets (good and corrupted) from the model which has nothing to do with how well the RX is receiving the TX

Option for this protocol corresponds to the CC2500 fine frequency tuning. This value is different for each Module and must be accurate otherwise the link will not be stable. Check the Frequency Tuning page to determine it.

CH1CH2CH3CH4CH5CH6CH7
AET_PITCHRT_HOLDIDLEMODE

IDLE= 3 pos switch: -100% Normal, 0% Idle1, +100% Idle2

From the TX manual: MODE= 3 pos switch -100% Attitude, 0% Attitude(?), +100% 3D For M2: MODE= 3 pos switch -100% 6G, 0% 3D, +100% 3D

Q303 - 31

Autobind protocol

CH1CH2CH3CH4
AETR

CC2500: only Q303 is supported.

Sub_protocol Q303 - 0

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

CH5CH6CH7CH8CH9CH10CH11
AHOLDFLIPPICTUREVIDEOHEADLESSRTHGIMBAL

GIMBAL needs 3 position -100%/0%/100%

Sub_protocol CX35 - 1

CH5CH6CH7CH8CH9CH10CH11
ARMVTXPICTUREVIDEORTHGIMBAL

ARM is 2 positions: land / take off

Each toggle of VTX will increment the channel.

Gimbal is full range.

Sub_protocol CX10D - 2

Models CX10D and CX33W

CH5CH6
ARMFLIP

ARM is 3 positions: -100%=land / 0%=manual / +100%=take off

Sub_protocol CX10WD - 3

CH5CH6
ARMFLIP

ARM is 3 positions: -100%=land / 0%=manual / +100%=take off

Q90C - 72

CH1CH2CH3CH4CH5CH6
AETRFMODEVTX+

FMODE: -100% angle, 0% horizon, +100% acro VTX+: -100%->+100% channel+

SLT - 11

Autobind protocol

Sub_protocol V1 - 0

CH1CH2CH3CH4CH5CH6
AETRGEARPITCH

Sub_protocol V2 - 1

CH1CH2CH3CH4CH5CH6CH7CH8
AETRCH5CH6CH7CH8

Sub_protocol Q100 - 2

Models: Dromida Ominus UAV

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRRATES-CH7CH8MODEFLIP--CALIB

RATES takes any value between -50..+50%: -50%=min rates, 0%=mid rates (stock setting), +50%=max rates

CH7 and CH8 have no visible effect

MODE: -100% level, +100% acro

FLIP: sets model into flip mode for approx 5 seconds at each throw of switch (rear red LED goes out while active) -100%..+100% or +100%..-100%

CALIB: -100% normal mode, +100% gyro calibration

Sub_protocol Q200 - 3

Model: Dromida Ominus Quadcopter FPV, the Nine Eagles - FENG FPV and may be others

Dromida Ominus FPV channels mapping:

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRRATES-CH7CH8MODEFLIPVID_ONVID_OFFCALIB

FENG FPV: channels mapping:

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRRATES-CH7CH8FLIPMODEVID_ONVID_OFFCALIB

RATES takes any value between -50..+50%: -50%=min rates, 0%=mid rates (stock setting), +50%=max rates

CH7 and CH8 have no visible effect

MODE: -100% level, +100% acro

FLIP: sets model into flip mode for approx 5 seconds at each throw of switch (rear red LED goes out while active) -100%..+100% or +100%..-100%

CALIB: -100% normal mode, +100% gyro calibration

Sub_protocol MR100 - 4

Models: Vista UAV, FPV, FPV v2

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRRATES-CH7CH8MODEFLIPVIDEOPICTURE

RATES takes any value between -50..+50%: -50%=min rates, 0%=mid rates (stock setting), +50%=max rates

CH7 and CH8 have no visible effect

FLIP: sets model into flip mode for approx 5 seconds at each throw of switch (rear red LED goes out while active) -100%..+100% or +100%..-100%

MODE: -100% level, +100% acro

Sub_protocol V1_4CH - 5

Transmitters: SLT2 and SLT2 DLC, Receivers: SPMXSE2825RX, SPMXSBER1025G, SPMXSE4510RX, ...

CH1CH2CH3CH4
CH1CH2CH3CH4

CH4 is used for DSC settings: -35% off to +15% full

Sub_protocol RF_SIM - 6

Models: the SLT-dongle included in RealFlight 7.5

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRCH5CH6CH7CH8CH9CH10

Output 10 channels to use with RealFlight simulator. The RealFlight "reset" button found on the RealFlight USB-transmitter, can now be CH9 or CH10.

RealFlight 8 crashes when trying to save file with reset-button defined.

Please save radio-profile with a new name without setting reset-button in RF8. Then edit the radio-profile definition in ~\Documents\RealFlight8\RadioProfiles\ in an ordinary fileeditor.

Find the [Reset21] section and change Input=INT:-1 to Input=INT:9

V911S - 46

CH1CH2CH3CH4CH5CH6
AETRCALIBRATE

Rate: -100% High, +100% Low

Sub_protocol V911S - 0

Models: WLtoys V911S, XK A110

Sub_protocol E119 - 1

Models: Eachine E119, JJRC W01-J3, XK A220 P-40, (TX X4-A800) A800 R2, F959S R2, (TX X4-A800) A160 R2, A280

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRCALIBRATE6G_3D6GSENIORLIGHT

A280 -> 6GSENIOR: -100% - 6G, +100% - Senior mode (turn off gyro), LIGHT: cycle the light through on-flash-off when the CH9 value is changed from -100% to 100%

WL91X - 106

Models: WLtoys WL911, WL913, WL915 and may be others...

CH1CH2CH3CH4
STTHST_TRTH_TR

XK - 62

CC2500: only X450 is supported.

Sub_protocol X450 - 0

Models: XK X450 (TX=X8)

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRFlight_modesTake_offEmerg stop3D/6GPictureVideo

Flight_modes: -100%=M-Mode, 0%=6G-Mode, +100%=V-Mode. CH6-CH10 are mementary switches.

Sub_protocol X420 - 1

Models: XK X420/X520 (TX=X4)

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRFlight_modesTake_offEmerg stop3D/6GPictureVideo

Flight_modes: -100%=M-Mode, 0%=6G-Mode, +100%=V-Mode. CH6-CH10 are mementary switches.

Model: Tiger Drone 1400782

CH1CH2CH3CH4CH11CH12
AETRFLIPLIGHT

Sub_protocol Cars - 2

Models: WLtoys cars 284131/284161/284010/124016/124017/144010 and Eachine EAT14

XK2 - 99

You must assign a different RX number for each receiver/plane. Otherwise the new receiver/plane ID will overwrite the previous one.

If a CC2500 is installed it will be used for this sub protocol. Option in this case is used for fine frequency tuning like any CC2500 protocols so check the Frequency Tuning page.

If only a NRF24L01 is installed then this sub protocol might be problematic because it is using the xn297L emulation with a transmission speed of 250kbps which doesn't work very well with every NRF24L01, this is an hardware issue with the authenticity and accuracy of the components.

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRRateModeHoverLightStunt

The plane does not need to be bound each time if it is powered on after the radio/protocol is on.

Telemetry is supported. The plane sends a battery status of good->empty which is visible in A1 (good=8.4V->empty=7.1V) and RSSI gets a dummy value of 100. For the Sky Viper Vector, the battery telemetry will still appear in A1 with good=8.4V->empty=7.1V despite being a 1S plane with a switch good/bad in reality at 3.3V.

The rudder trim is driven from the rudder channel to increase the range (Original TX rudder has no range once the motor has been turned on...).

Mode: -100%=6G, 0%=3D, +100%=Gyro off (Senior mode)

Stunt: Sky Viper Vector

Sub_protocol X4 - 0

Transmitter: XK X4-A160, X5S, model: XK A160S, XK A280, XK A300

Model: Sky Viper Vector

Sub_protocol P10 - 1

Model: Park10 J3-CUB


NRF24L01 RF Module

ASSAN - 24

Extended limits supported

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

The transmitter must be close to the receiver while binding.

BAYANG - 14

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11--CH14CH15
AETRFLIPRTHPICTUREVIDEOHEADLESSINVERTEDRATES--ANAAUX1ANAAUX2

RATES: -100%(default)=>higher rates by enabling dynamic trims (except for Headless), 100%=>disable dynamic trims

Channels 14 and 15 (ANAAUX1 and ANAAUX2) only available with analog aux channel option, indicated below.

Sub_protocol BAYANG - 0

Models: Eachine H8(C) mini, BayangToys X6/X7/X9, JJRC JJ850, Floureon H101 ...

Option=0 or Telemetry = Off -> normal Bayang protocol

Option=1 or Telemetry = On -> enable telemetry with Silverxxx firmware. Value returned to the TX using FrSkyD Hub are RX RSSI, TX RSSI, A1=uncompensated battery voltage (set the ratio to 5.0 and adjust with offset), A2=compensated battery voltage (set the ratio to 5.0 and adjust with offset) and if supported AccX=P, AccY=I, ACCZ=D (which you can rename after the sensors discovery)

Option=2 or Telemetry = Off+AUX -> enable analog aux channels with NFE Silverware firmware. Two otherwise static bytes in the protocol overridden to add two 'analog' (non-binary) auxiliary channels.

Option=3 or Telemetry = On+AUX-> both Silverware telemetry and analog aux channels enabled.

Sub_protocol H8S3D - 1

Model: H8S 3D

Same channels assignment as above.

Sub_protocol X16_AH - 2

Model: X16 AH

CH12
TAKE_OFF

Sub_protocol IRDRONE - 3

Model: IRDRONE

CH12CH13
TAKE_OFFEMG_STOP

Sub_protocol DHD_D4 - 4

Model: DHD D4

CH12CH13
TAKE_OFFEMG_STOP

Sub_protocol QX100 - 5

Model: REVELL QX100

BAYANG RX - 59

The Bayang receiver protocol enables master/slave trainning, separate access from 2 different radios to the same model,...

See the BAYANG protocol on how to activate ANAUX1 and ANAUX2 (Option/Telemetry=2).

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRANAUX1ANAUX2FLIPRTHPICTUREVIDEO

Sub_protocol Multi - 0

Use the telemetry to send the trainer information to the radio. Available in OpenTX 2.3.3, Trainer Mode Master/Multi

Sub_protocol CPPM - 1

Sending trainer channels to FrSky radios through telemetry does not work since the telemetry lines of the internal and external modules are shared (hardware limitation). On a STM32 module and with a simple hardware modification, you can go around this limitation using CPPM to send the trainer information to the radio. For more information check the CCPM Hardware Modification page.

Once your setup is complete and before enabling the internal module, you must check the "Disable Telemetry" box to stop the Multi module from sending any data to the radio and therfore freeing up the line for the internal module.

BUGSMINI - 42

Models: MJX Bugs 3 Mini and 3H

Telemetry enabled for RX RSSI, Battery voltage good/warning/bad

RX_Num is used to give a number to a given model. You must use a different RX_Num per MJX Bugs Mini. A maximum of 16 Bugs Mini are supported.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRARMANGLEFLIPPICTUREVIDEOLED

ANGLE: angle is +100%, acro is -100%

Sub_protocol BUGSMINI - 0

Sub_protocol BUGS3H - 1

CH11
ALTHOLD

Cabell - 34

Homegrown protocol with variable number of channels (4-16) and telemetry (RSSI, V1, V2).

It is a FHSS protocol developed by Dennis Cabell (KE8FZX) using the NRF24L01+ 2.4 GHz transceiver. 45 channels are used frequency hop from 2.403 through 2.447 GHz. The reason for using 45 channels is to keep operation within the overlap area between the 2.4 GHz ISM band (governed in the USA by FCC part 15) and the HAM portion of the band (governed in the USA by FCC part 97). This allows part 15 compliant use of the protocol, while allowing licensed amateur radio operators to operate under the less restrictive part 97 rules if desired.

Additional details about configuring and using the protocol are available at the RX project at: https://github.com/soligen2010/RC_RX_CABELL_V3_FHSS

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
AETRAUX1AUX2AUX3AUX4AUX5AUX6AUX7AUX8AUX9AUX10AUX11AUX12

Sub_protocol CABELL_V3 - 0

4 to 16 channels without telemetry

Sub_protocol CABELL_V3_TELEMETRY - 1

4 to 16 channels with telemetry (RSSI, V1, V2). V1 & V2 can be used to return any analog voltage between 0 and 5 volts, so can be used for battery voltage or any other sensor that provides an analog voltage.

Sub_protocol CABELL_SET_FAIL_SAFE - 6

Stores failsafe values in the RX. The channel values are set when the sub-protocol is changed to 6, so hold sticks in place as the sub-protocol is changed.

Sub_protocol CABELL_UNBIND - 7

The receiver bound to the model is un-bound. This happens immediately when the sub-protocol is set to 7.

CG023 - 13

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPLIGHTPICTUREVIDEOHEADLESS

Sub_protocol CG023 - 0

Models: EAchine CG023/CG031/3D X4

Sub_protocol YD829 - 1

Models: Attop YD-822/YD-829/YD-829C ...

CH5CH6CH7CH8CH9
FLIPPICTUREVIDEOHEADLESS

CX10 - 12

Autobind protocol

CH1CH2CH3CH4CH5CH6
AETRFLIPRATE

Rate: -100%=rate 1, 0%=rate 2, +100%=rate 3

Sub_protocol GREEN - 0

Models: Cheerson CX-10 green pcb

Same channels assignement as above.

Sub_protocol BLUE - 1

Models: Cheerson CX-10 blue pcb & some newer red pcb, CX-10A, CX-10C, CX11, CX12, Floureon FX10, JJRC DHD D1

CH5CH6CH7CH8
FLIPRATEPICTUREVIDEO

Rate: -100%=rate 1, 0%=rate 2, +100%=rate 3 or headless for CX-10A

Sub_protocol DM007 - 2

CH5CH6CH7CH8CH9
FLIPMODEPICTUREVIDEOHEADLESS

Sub_protocol JC3015_1 - 4

CH5CH6CH7CH8
FLIPMODEPICTUREVIDEO

Sub_protocol JC3015_2 - 5

CH5CH6CH7CH8
FLIPMODELEDDFLIP

Sub_protocol MK33041 - 6

CH5CH6CH7CH8CH9CH10
FLIPMODEPICTUREVIDEOHEADLESSRTH

DM002 - 33

Autobind protocol

Only 3 TX IDs available, change RX_Num value 0-1-2 to cycle through them

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLEDCAMERA1CAMERA2HEADLESSRTHRATE_LOW

E016H - 85

Autobind protocol

Model: Eachine E016H

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRSTOPFLIP-HEADLESSRTH

EazyRC - 61

Autobind protocol

CH1CH2CH3CH4
STEERINGTHROTTLE

ESKY - 16

CH1CH2CH3CH4CH5CH6
AETRGYROPITCH

Sub_protocol Std - 0

Sub_protocol ET4 - 1

Models compatible with the ET4 transmitter like ESky Big Lama Multiple IDs but only one frequency...

ESKY150 - 35

ESky protocol for small models since 2014 (150, 300, 150X, ...)

Sub_protocol 4CH - 0

CH1CH2CH3CH4
AETR

Sub_protocol 7CH - 1

CH1CH2CH3CH4CH5CH6CH7
AETRFMODEAUX6AUX7

FMODE and AUX7 have 4 positions: -100%..-50%=>0, -50%..5%=>1, 5%..50%=>2, 50%..100%=>3

FX - 58

FEI XIONG

Sub_protocol FX816 - 0

Model: FX816 P38, B17

Only 8 TX IDs available

CH1CH2CH3CH4
A-T-

Sub_protocol FX620 - 1

Model: FX620 SU35

CH1CH2CH3CH4
A-T-

Sub_protocol 9630 - 2

Model: FX9630, FX9603, QIDI-550

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRRATEGYROTrimRTrimATrimE

FX9630 and FX9603 Gyro: -100%=6G small throw, 0%=6G large throw, +100%=3D

QIDI-550 Gyro: -100%=3D, 0%=6G, +100%=Torque

Sub_protocol Q560 - 3

Model: QIDI-560, QIDI-580 (Cirrus SR22)

CH1CH2CH3CH4CH5CH6CH7
AETRFLIPGYROLEDs

FLIP is a toggle channel meaning that -100% to +100% is a command and +100% to -100% is also a command

  • GYRO QIDI-560: -100%=6G, 0%=3D+Gyro, +100%=3D
  • GYRO QIDI-580: -100%=6G, 0%=6G+Inverted, +100%=3D+Gyro

Sub_protocol QF012 - 4

Model: QF012 SBD Dauntless

Telemetry supported. The plane sends a battery status of good->empty which is visible in A1 (good=4.2V->empty=3.1V) and RSSI gets a dummy value of 100.

CH1CH2CH3CH4CH5CH6CH7CH8
AETRFLIPGYROInvertReset

Gyro: -100%=6G, 0%=3D+Gyro, +100%=3D

Reset: Restore fine tunning midpoint

Sub_protocol BM26 - 5

Model: BM26 P51

Telemetry supported. The plane sends a battery status of good->empty which is visible in A1 (good=4.2V->empty=3.1V) and RSSI gets a dummy value of 100.

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPGYROLEDsTurning Light switchCalib

Gyro: -100%=6G, 0%=3D+Gyro, +100%=3D

Sub_protocol A570 - 6

VTOL Model: Kootai A570, QIDI-570

This model has no telemetry. Low battery indicated by model LED's turning flashing red.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRSTOPMODERateColorLED-OffTrimRTrimATrimE
  • STOP: -100% allows standard start / sticks moved down and center (Mode 2), +100% all motors stop
  • MODE: -100%=Vertical hover, 0%=Flat flight, +100%=Vertical flight (Original TX will not allow motor start in Flat flight)
  • Rate: -100%=Low Rate, +100%=High Rate
  • Color: -100% / +100% toggles LED lights through color choices
  • LED-Off: +100% switches lights OFF, -100% allows lights ON after a toggle of the color channel
  • Trims: -100%=Rud-L,Ail-L,Ele-Back, +100%=Rud-R,Ail-R,Ele-Fwd, if used must be tied to momentary 3-pos switches
  • (trim switches disabled in FM tab, added to trim channels 10,11,12 in mixes tab)

Calibration: Same as original TX, model on level surface, TX bound, sticks lower left corners, LED's flashing

FY326 - 20

Sub_protocol FY326 - 0

Model: FY326 Q7 Quadcopter

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPRTHHEADLESSEXPERTCALIBRATE

Sub_protocol FY319 - 1

Model: X6 FY319 Quadcopter (Needs Testing)

FQ777 - 23

Autobind protocol

Sub_protocol 124 - 0

Model: FQ777-124 (with SV7241A)

CH1CH2CH3CH4CH5CH6CH7CH8
AETRFLIPRTHHEADLESSEXPERT

Sub_protocol XBM37 - 1

Model: T-Smart XBM-37 (with SV7241A)

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14
AETRRATEFLIPHEADLESSLEDPICTUREVIDEORTHOKETrimAtrim
  • RATE: -100% Low, 0% Mid, +100% High
  • CH6 to CH12 are OFF/-100 and ON/+100 exception LED is OFF/+100
  • Receiver numbers (0-63) available for model match, MPM global ID used for unique module identifier.
  • Changing the TX module or RX number will require re-binding the receiver.

Calibration: Set quad on level surface, pull both sticks down in outer corners until LED's flash (Mode-2 TX)

GW008 - 32

Model: Global Drone GW008 from Banggood

There are 3 versions of this small quad, this protocol is for the one with a XNS104 IC in the stock Tx and PAN159CY IC in the quad. The xn297 version is compatible with the CX10 protocol (green pcb). The LT8910 version is not supported yet.

CH1CH2CH3CH4CH5
AETRFLIP

H36 - 103

Autobind protocol

Model: JJRC H36 (JR-NH010R9 board)

CH1CH2CH3CH4CH5CH6CH7
AETRFLIPHEADLESSRTH

H8_3D - 36

Autobind protocol

Sub_protocol H8_3D - 0

Models: Eachine H8 mini 3D,Eachine E10, JJRC H20/H22/H11D

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRFLIPLIGTHPICTUREVIDEOOPT1OPT2CAL1CAL2GIMBAL

JJRC H20: OPT1=Headless, OPT2=RTH

JJRC H22: OPT1=RTH, OPT2=180/360° flip mode

H8 3D: OPT1=RTH then press a direction to enter headless mode (like stock TX), OPT2=switch 180/360° flip mode

CAL1: H8 3D acc calib, H20/H20H headless calib CAL2: H11D/H20/H20H acc calib

Sub_protocol H20H - 1

CH6=Motors on/off

Sub_protocol H20 Mini - 2

Only 3 TX IDs available, change RX_Num value 0-1-2 to cycle through them

Sub_protocol H30 Mini - 3

Only 4 TX IDs available, change RX_Num value 0-1-2_3 to cycle through them

HISKY - 4

Sub_protocol Hisky - 0

CH1CH2CH3CH4CH5CH6CH7CH8
AETRGEARPITCHGYROCH8

GYRO: -100%=6G, +100%=3G

Sub_protocol HK310 - 1

Models: RX HK-3000, HK3100 and XY3000 (TX are HK-300, HK-310 and TL-3C)

Failsafe supported

CH1CH2CH3CH4CH5
TRAUX

KN - 9

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRDRTHOLDIDLEUPGYROTtrimAtrimEtrimRtrimHoverDebugging

Dual Rate: +100%=full range, Throttle Hold: +100%=hold, Idle Up: +100%=3D, GYRO: -100%=6G, +100%=3G

Sub_protocol WLTOYS - 0

Models: V966/V977/F959S/A160 J3/...

Sub_protocol FEILUN - 1

HONTAI - 26

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLEDPICTUREVIDEOHEADLESSRTHCAL

Sub_protocol HONTAI - 0

Sub_protocol JJRCX1 - 1

CH6
ARM

Sub_protocol X5C1 clone - 2

Sub_protocol FQ777_951 - 3

Sub_protocol XKK170 - 3

Model: XK K170 UH-60L Black hawk, XK K270 UH-60L

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRRATEEMERGENCYTAKE_OFF/LANDINGCALIBTrimATrimEOptical

RATE: -100% Low, 0% Mid, +100% High

Optic: enable/disable the optical flow sensor for K270

JIABAILE - 102

Sub_protocol Std - 0

Models: JBL-430x 1:43 car without gyro

You must assign a different RX number for each car. Otherwise the new car ID will overwrite the previous one.

CH1CH2CH3CH4CH5CH6CH7
STTH-ST_TRIMSPEEDLIGHTFLASH
  • Extended Steering comparing to original
  • SPEED: -100% High, 0% Mid, +100% Low
  • ST_TRIM: value between -100% and +100% but using the radio steering trim looks better

Sub_protocol Gyro - 1

Models: JBL-430x 1:43 car with gyro

CH1CH2CH3CH4CH5CH6CH7
STTHGYROST_TRIMSPEEDLIGHTFLASH
  • Extended Steering comparing to original
  • SPEED: -100% High, 0% Mid, +100% Low
  • GYRO: -100% Off..+100% Max
  • ST_TRIM: momentary switch, -100% Trim left, 0% Idle, +100% Trim right. Configure the radio steering trim has buttons (ST- and ST+) and assign them to that channel. Don't forget to disable the steering trim in the driving modes.

JJRC345 - 71

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPHEADLESSRTHLEDUNK1UNK2UNK3

Sub_protocol JJRC345 - 0

Model: JJRC345

Sub_protocol SkyTmblr - 1

Model: DF-Models SkyTumbler

RTH not supported

KAMTOM - 104

Models: KAMTOM RC Racing KM24xx (KM32xx?), Pinecone SG-24xx

CH1CH2CH3CH4CH5CH6CH7
STTHUNK1UNK2ST_TRTH_TRTH_DR

Low battery telemetry in A1 with 0 = low batt

KYOSHO2 - 93

Model: TX KT-17, Minium Edge 540, Minium Citabria

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10

LOLI - 82

LOLI3 receivers: https://github.com/wooddoor/Loli3

Failsafe supported. Once failsafe values for the 8 channels have been configured in Custom mode, wait for the RX to learn them, then set Failsafe to Receiver.

Telemetry supported: RX RSSI, TX LQI (percentage of received telemetry packets), A1 and A2 with a Ratio=25.5 and Offset=0.

Extended limits supported.

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

RX features can be configured using the multiLOLI LUA script on OpenTX or manually using the table below:

Config onFor channelSwitchServoPPMSBUSPWM
CH9CH1-100%0%+50%-+100%
CH10CH2-100%0%--+100%
CH11CH3-100%0%---
CH12CH4-100%0%---
CH13CH5-100%0%-+50%-
CH14CH6-100%0%--
CH15CH7-100%0%--+100%
CH16CH8-100%0%---

MouldKg - 90

Mould King 2.4GHz TX: Technic Brick models

Sub_protocol A4444 - 0

Model: 4 analog ports brick

Up to 4 bricks can be controlled at the same time.

Option fieldValue
0The module will act like the original radio which will bind every time and attach to the first brick in bind mode
1The module will control the brick number RX_num
2The module will control the brick number RX_num and RX_num+1
3The module will control the brick number RX_num, RX_num+1 and RX_num+2
4The module will control the brick number RX_num, RX_num+1, RX_num+2 and RX_num+3

To associate a brick to a RX number (RX_num above), set this RX number under the protocol, set option to 1, launch a bind and power on the brick you want to control. Repeat this for every brick using a different RX number each time and then indicate the number of bricks to be controlled using the Option field.

Example: I want to control 2 bricks. I select RX number 1, set option to 1 and launch a bind on the first brick. I select RX number 2, set option to 1 and launch a bind on the second brick. Now to control both bricks I set RX number to 1 and option to 2. Therefore brick1 will react to channels CH1 to CH4 and brick2 to channel CH5 to CH8. On another model I can control 4 other bricks, bind each brick to RX number 3 to 6 and then finaly set RX number to 3 and option to 4 to contol the 4 bricks with CH1 to CH16.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
Brick1_ABrick1_BBrick1_CBrick1_DBrick2_ABrick2_BBrick2_CBrick2_DBrick3_ABrick3_BBrick3_CBrick3_DBrick4_ABrick4_BBrick4_CBrick4_D

Sub_protocol D4444 - 1

Model: 4 digital ports brick and Integrated power module

Up to 4 bricks can be controlled at the same time.

Option fieldValue
0The module will act like the original radio which will bind every time and attach to the first brick in bind mode
1The module will control the brick number RX_num
2The module will control the brick number RX_num and RX_num+1
3The module will control the brick number RX_num, RX_num+1 and RX_num+2
4The module will control the brick number RX_num, RX_num+1, RX_num+2 and RX_num+3

To associate a brick to a RX number (RX_num above), set this RX number under the protocol, set option to 1, launch a bind and power on the brick you want to control. Repeat this for every brick using a different RX number each time and then indicate the number of bricks to be controlled using the Option field.

Example: I want to control 2 bricks. I select RX number 1, set option to 1 and launch a bind on the first brick. I select RX number 2, set option to 1 and launch a bind on the second brick. Now to control both bricks I set RX number to 1 and option to 2. Therefore brick1 will react to channels CH1 to CH4 and brick2 to channel CH5 to CH8. On another model I can control 4 other bricks, bind each brick to RX number 3 to 6 and then finaly set RX number to 3 and option to 4 to contol the 4 bricks with CH1 to CH16.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
Brick1_ABrick1_BBrick1_CBrick1_DBrick2_ABrick2_BBrick2_CBrick2_DBrick3_ABrick3_BBrick3_CBrick3_DBrick4_ABrick4_BBrick4_CBrick4_D

Sub_protocol A664 - 2

Model: 4/6 analog ports brick

Up to 3 bricks can be controlled at the same time. The bricks can be either 4 or 6 ports but only the 2 first bricks will be sent 6 channels, the last brick will only be sent 4 channels.

Option fieldValue
0The module will act like the original radio which will bind every time and attach to the first brick in bind mode
1The module will control the brick number RX_num
2The module will control the brick number RX_num and RX_num+1
3The module will control the brick number RX_num, RX_num+1 and RX_num+2

To associate a brick to a RX number (RX_num above), set this RX number under the protocol, set option to 1, launch a bind and power on the brick you want to control. Repeat this for every brick using a different RX number each time and then indicate the number of bricks to be controlled using the Option field.

Example: I want to control 2 bricks. I select RX number 1, set option to 1 and launch a bind on the first brick. I select RX number 2, set option to 1 and launch a bind on the second brick. Now to control both bricks I set RX number to 1 and option to 2. Therefore brick1 will react to channels CH1 to CH4 and brick2 to channel CH5 to CH8. On another model I can control 3 other bricks, bind each brick to RX number 3 to 5 and then finaly set RX number to 3 and option to 3 to contol the 4 bricks with CH1 to CH16.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
Brick1_ABrick1_BBrick1_CBrick1_DBrick1_EBrick1_FBrick2_ABrick2_BBrick2_CBrick2_DBrick2_EBrick2_FBrick3_ABrick3_BBrick3_CBrick3_D

NCC1701 - 44

Model: Air Hogs Star Trek USS Enterprise NCC-1701-A

Autobind protocol

Telemetry: RSSI is a dummy value. A1 voltage is dummy but used for crash detection. In case of a crash event A1>0V, you can assign a sound to be played on the TX in that case (siren on the original transmitter).

Only 9 IDs available, cycle through them using RX_Num.

CH1CH2CH3CH4CH5
AETRWarp

Potensic - 51

Model: Potensic A20

CH1CH2CH3CH4CH5CH6CH7CH8
AETRTAKE_OFF/LANDINGEMERGENCYMODEHEADLESS

TAKE_OFF/LANDING: momentary switch -100% -> +100%

EMERGENCY: Stop +100%

MODE: Beginner -100%, Medium 0%, Advanced +100%

HEADLESS: Off -100%, On +100%

PROPEL - 66

Model: PROPEL 74-Z Speeder Bike

Autobind protocol

Telemetry: RSSI is equal to TX_LQI which indicates how well the TX receives the RX (0-100%). A1 (with a ratio of 25.5) voltage should indicate the numbers of life remaining 0.2->0.1->0.0(not tested). A2 (with a ratio of 25.5) is giving the model status: 12.8=flying, 0.8=taking off, 0.4=landing, 0=landed/crashed

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14
AETRLEDsRollCWRollCCWFireWeaponsCalibAlt_HoldTake_offLandTraining

Q2X2 - 29

Sub_protocol Q222 - 0

Models: Q222 v1 and V686 v2

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRFLIPLEDMODULE2MODULE1HEADLESSRTHXCALYCAL

Sub_protocol Q242 - 1 and Q282 - 2

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRFLIPLEDPICTUREVIDEOHEADLESSRTHXCALYCAL

Model: JXD 509 is using Q282 with CH12=Start/Stop motors

Realacc - 76

Model: Realacc R11, Eachine E017

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLIGHTCALIBHLESSRTHTHR_CUTROTATE

Redpine - 50

Link to the forum

Sub_protocol FAST - 0

Sub_protocol SLOW - 1

SGF22 - 97

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12
AETRMODEFLIPLIGHTPHOTOVIDEOTRIMRESETBALBALHIG

Telemetry is supported. The plane sends a battery status of good->empty which is visible in A1 (good=13.2V->empty=0V) and RSSI gets a dummy value of 100.

Sub_protocol F22

Model: SG F22

Mode: -100% = 3D, 0% = 6G, 100% = Vertical

Model: FlyBear FX922

Manual CH11=-100% & CH12=-100%, Balance CH11=+100% & CH12=-100%, Large Angle Balance CH11=-100% & CH12=+100%

Sub_protocol F22S

Model: ParkTen F22S

Mode -100% = 3D, 0% = 6G

Sub_protocol J20

Model: KF700 J20

Mode -100% = Gyro off, 0% = Horizontal, 100% = Vertical. CH8 - Invert, CH10 - Fix Height (Altitude hold)

Sub_protocol CX10

Model: Cheerson CX-10 with red PCB

Only 2 IDs available, use RX num to cycle through them.

Mode -100% = Low, 0% = Medium, 100% = High

Shenqi - 19

Autobind protocol

Model: Shenqiwei 1/20 Mini Motorcycle

CH1CH2CH3CH4
--TR

Throttle +100%=full forward,0%=stop,-100%=full backward.

Shenqi2 - 105

Autobind protocol

Model: Shenqiwei 1/20 Mini Motorcycle

CH1CH2
STTH

Symax - 10

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPRATESPICTUREVIDEOHEADLESS

RATES: -100%(default)=>disable dynamic trims, +100%=> higher rates by enabling dynamic trims (except for Headless)

Sub_protocol SYMAX - 0

Models: Syma X5C-1/X11/X11C/X12

Sub_protocol SYMAX5C - 1

Model: Syma X5C (original) and X2

V2X2 - 5

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPLIGHTPICTUREVIDEOHEADLESSMAG_CAL_XMAG_CAL_Y

Sub_protocol V2x2 - 0

Models: WLToys V202/252/272/A959/K969/K979/K989/K999, JXD 385/388, JJRC H6C, Yizhan Tarantula X6 ...

PICTURE: also automatic Missile Launcher and Hoist in one direction

VIDEO: also Sprayer, Bubbler, Missile Launcher(1), and Hoist in the other dir

Sub_protocol JXD506 - 1

Model: JXD 506

CH10CH11CH12
Start/StopEMERGENCYCAMERA_UP/DN

Sub_protocol MR101 - 2

TX: MR101, model: Dromida XL

Only 1 ID available. If you have a TX contact me on GitHub or RCGroups.

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRFLIPPICTUREVIDEOMOT_ON_OFFAUTO

MOT_ON_OFF: momentary switch (you need to maintaint it for at least 1.5sec for on or off)

AUTO: Land=-100% Takeoff=+100%

The model can work with a none centered throttle.

V761 - 48

Gyro: -100%=Beginner mode (Gyro on, yaw and pitch rate limited), 0%=Mid Mode ( Gyro on no rate limits), +100%=Mode Expert Gyro off

Calib: momentary switch, calib will happen one the channel goes from -100% to +100%

Flip: momentary switch: hold flip(+100%), indicate flip direction with Ele or Ail, release flip(-100%)

RTN_ACT and RTN: -100% disable, +100% enable

Sub_protocol 3CH - 0

Models: Volantex V761-1, V761-3 and may be others

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
-ETRGYROCALIBFLIPRTN_ACTRTNBEEP

Sub_protocol 4CH - 1

Models: Volantex V761-4+ and Eachine P51-D, F4U, F22 and may be others

If the model (761-11 and above) sends telemetry then the battery status ok/empty is in A1 (4.4V -> 2.2V) and RSSI gets a dummy value of 100.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10
AETRGYROCALIBFLIPRTN_ACTRTNBEEP

Sub_protocol TOPRC - 2

Models: Top RC Hobby Spitfire, P51D, BF-109

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRGYROCALIBFLIPRTN_ACTRTN

WPL - 107

TX: "Basic", Models: D12 / D12KM / D22 / D32 / D42 / D14

Only 1 ID available. If you have a TX contact me on GitHub or RCGroups.

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7
THSTST_TrimAuxLightTH_RateST_Rate

Light: -100%=Off, +100%=On, Rate: -100%=Low, +100%=High

XERALL - 91

Model: Xerall TankCopter

To bind/link the model faster put the throttle low before powering up the model.

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13
AETRFly/TankTakeoff/Land/EmergRateHeadLessPhotoVideoTrimRTrimETrimA

Fly/Tank: -100%=Fly, +100%=Tank

Takeoff/Land/Emerg: momentary switch -100%->+100%, same switch for all 3 functions. For Takeoff throttle must be centered before actionning the momentary switch. For Emergency stop hold the momentary switch for a few sec.

Unlock the motors is achieved like on the original radio by putting sticks in the bottom corners (position depends on your mode 1,2,3,4) and throttle has to be raised to center before recentering the sticks for the motors to keep spinning. Takeoff happens as soon as the throttle goes above center.

Rate: -100%=Low, +100%=High

HeadLess: -100%=Off, +100%=On

Photo: momentary switch -100%->+100% (short press on the original remote)

Video: -100%=Off, +100%=On (long press on the original remote)

YD717 - 8

Autobind protocol

CH1CH2CH3CH4CH5CH6CH7CH8CH9
AETRFLIPLIGHTPICTUREVIDEOHEADLESS

Sub_protocol YD717 - 0

Sub_protocol SKYWLKR - 1

Sub_protocol SYMAX4 - 2

Sub_protocol XINXUN - 3

Sub_protocol NIHUI - 4

Same channels assignement as above.

YuXiang - 100

Models: E190 F07 UH-1D, E186 F08 Bell-206

Telemetry A1=Batt voltage with a Ratio 3.5 and Offset 7, A2=Low batt with 0=OK, everything else=BAD

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11
AETRLOCKRATELANDMANUALFLIPMODEPITCH

ZSX - 52

Model: JJRC ZSX-280

Autobind protocol

CH1CH2CH3CH4CH5
--TRLIGHT

SX1276 RF Module

FRSKYR9 - 65

R9 RXs must be flashed with latest ACCST.

Extended limits and failsafe supported.

Full telemetry supported.

Notes:

  • The choices of CH1-8/CH9-16 and Telem ON/OFF is available in OpenTX 2.3.10 nightlies. The default is CH1-8 Telem ON.
  • Telemetry from TX to RX is available in OpenTX 2.3.10 nightlies.
  • Power adjustment is not supported on the T18.

Sub_protocol R9_915 - 0

FLEX 915MHz, 16 channels

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol R9_868 - 1

FLEX 868MHz, 16 channels

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol R9_915_8CH - 2

FLEX 915MHz, 8 channels

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol R9_868_8CH - 3

FLEX 868MHz, 8 channels

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

Sub_protocol R9_FCC - 4

FCC, 16 channels

CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16
CH1CH2CH3CH4CH5CH6CH7CH8CH9CH10CH11CH12CH13CH14CH15CH16

Sub_protocol R9_FCC_8CH - 6

FCC, 8 channels

CH1CH2CH3CH4CH5CH6CH7CH8
CH1CH2CH3CH4CH5CH6CH7CH8

OpenLRS module

OpenLRS - 27

This is a reservation for OpenLRSng which is using Multi's serial protocol for their modules: https://openlrsng.org/. On the Multi side there is no protocol affected on 27 so it's just ignored.