Support/FAQ for Pro Templates

Mike Shellim
Last updated 9 Jan 2019

This page is for support of the Pro templates, though some of the material will also be of general interest. Here you can find out the recommended versions of OpenTx, how to migrate your templates to a different transmitter or to a newer version of OpenTx, and any current issues affecting the Pro templates.

Which transmitters can I use with the Pro templates?

The FrSky X9D, X9D Plus, X9E, X10 and X12 may be used with all current templates.

The Q-X7 may be used with the F3F, Wingy and Ahi templates. Other templates will require modification due to the Q-X7's lack of sliders.

What are the recommended versions of OpenTx?

Currently, there are two branches of OpenTx which are officially supported by the OpenTx developers. Each branch has its own data format.

OpenTx 2.2

This is the latest branch. All current Pro templates are fully compatible with OpenTx 2.2.1 and later. Do not use OpenTx 2.2.0 or release candidates ('RC') - these have bugs.

OpenTx 2.1

This is an older branch. Although still officially supported, it's unlikely that the devs will continue to update it. Recommended version is 2.1.9. Some templates are compatible - please check the template's download page. If the latest version is not compatible with 2.1, there may be an older version which is compatible (see template's version history), however it will not have all the latest features.

Known issues with Pro templates

There are no known issues affecting current templates when used with recommended versions of OpenTx :-))

Migrating from OpenTx 2.1 to 2.2

If you're running OpenTx 2.1, then at some stage you may wish to flash your transmitter to OpenTx 2.2, in order to gain access to new features in OpenTx, or run the newer Pro templates. I won't describe the procedure (there are other resources for this). Suffice to say that once flashing is complete, the data in your transmitter will be automatically converted to 2.2 format the next time you power up. There are a couple of potential issues to be aware of:

Custom sounds no longer work after upgrading from OpenTx 2.1 to 2.2
After upgrading, you may find that some setups have 'lost' some sounds even though the .wav files are present on the SD card. This is due to a 6-character limit for filenames introduced in 2.2. To fix this, you'll need to identify all the sounds files used (these are shown in the Special Functions menu). In the SD card, shorten the names of these files to 6 characters + '.wav', then update the references in the Special Functions menu.
Note: sound files for all current Pro templates satisfy the 6-character limit.
Servo centres shift after upgrading from OpenTx 2.1 to 2.2
There are two possible causes for shifting centres:
1. Sticks/sliders not calibrated after flashing. Calibrate and check.
2. A known bug in OpenTx 2.1: channel values are not correctly calculated. This bug was fixed in OpenTx 2.2; after migration to 2.2, any channels with PPM Centre values other than the default 1500 will be slightly offset. Readjust the PPM Centre value to correct this (if using the Pro templates, this should be done in CAL mode).

Using the Pro templates with non-X9D transmitters

The Pro templates target the X9D. However it's easy to convert the data for a different supported transmitter. In Companion, make sure that your new transmitter is specified in the active profile. When the template is opened, a warning is displayed that the data is for a different transmitter, before the data is converted. Usually conversion works fine, but there are a couple of things to be aware of:

Knobs or sliders may not function after conversion
Mixer sources 'LS', 'RS', 'S1' and 'S2' may not be translated correctly. For all current templates, the setup guides contain detailed instructions for checking and fixing the affected mixers. (In practice, OpenTx 2.2 seems to handle the conversion correctly, so no changes should be needed).
A compatibilty warning is displayed in Companion
Starting with version 2.2.2, Companion displays warnings if it finds a possible issue when converting data to a different transmitter. Not all warnings require user action however (usually the conversions will have been performed correctly). In the example below, the source (SRC) of four mixes needs to be verified and if necessary altered to 'S2'.

Companion warnings

Copying model data to a second transmitter

How do I copy all my model data to a second transmitter?
You can migrate all your model data to a second transmitter as long as the target transmitter has the same or higher major version of OpenTx. The source and target transmitters do not need to be the same type (see also section above "Using the Pro templates with non-X9D transmitters").
To copy your models and settings to the target transmitter: start Companion (the version of Companion must match the version of OpenTx on the target transmitter). Connect the first transmitter and "backup radio to file". Still in Companion, select a profile for the target transmitter, then "file open" the backup file from the previous step; the model data is automatically converted for the target transmitter. Check any conversion issues reported by Companion and fix. Next, connect the target transmitter and transfer the data using "write models and settings". Copy all model-specific sound files to the target's SD card. Finally, don't forget to calibrate the sticks.

Missing GVARs menu

I cannot see the GVARs menu, how do I get it back?
I've received a report of a transmitter which was apparently supplied ex-factory with the GVARs menu missing. Unfortunately the GVARs menu is pretty well essential for all but the simplest models. The solution is to flash the transmitter with the latest version of OpenTx, ensuring that the NOGVARS option is unchecked in Companion Settings -> Build options. (The recommended build options for the Pro templates are: NOHELI, and LUA checked; all others unchecked.)

Changing the channel order

How do I re-order the servo channels (e.g. for mixed S-Bus/PWM operation)?
Re-ordering of servo channels can be done via a Lua script or manually. For more info see here.

Checking for errors

I think I may have made a date entry error, do I have to start again?
If you suspect you made a data entry error in Companion, then there's no need to start again. Load a .eepe or .otx file containing a known working version of the template, and use Companion's 'Compare models' tool to compare the two setups.

Historical issues

Issues affecting older templates and versions of OpenTx:

Date Problem description
2017-10-23 [OpenTx 2.2.0] Cannot calibrate flap neutral (fixed in 2.2.1)
2017-12-05 [OpenTx 2.2.1 RC1] GV's corrupted in Companion after conversion
2017-04-07 [OpenTx 2.2 RC14/ N366] Cannot reverse left flap CH4
2017-04-06 [E-Soar and E-Soar Plus] CAL and/or arming gesture not recognised
2017-02-17 [E-Soar Plus 2.0 & OTX 2.2] Timer starts at startup
2016-12-23 [F3J/TD 3.0.0 & X9E] 'Speed' callout not working
2016-02-01 [X9E] LS, RS not mapped correctly on X9E
2015-10-03 [OpenTx 2.1.2 - 2.1.4] Can't switch flight modes
2014-11-05 [F3F 3.0.0] Incorrect Inputs spec

Bug reports

If you find an issue, please email me with the following detailed info:

If there's insufficient info to reproduce the problem, I'll just pass it back, so please take the time to document the steps carefully.


Official OpenTx website:


Comments and queries are always welcome, I can be contacted by email.