Support/FAQ for Pro Templates

Mike Shellim
Last updated 12 August 2018

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.

OpenTx versions and data formats

OpenTx versions are specified by three numbers for example '2.2.2'.

The first two numbers denote the major version. Currently both 2.1 and 2.2 are in wide use. A major version is released when there are significant changes which necessitate a new data format. Model data can be converted from a lower format to higher, but not vice versa.

The third number denotes the minor version, for example 2.2.2. Minor versions contain bug fixes and minor feature additions. No data conversion involved when flashing a minor upgrade.

Latest stable versions

The latest stable releases of OpenTx are 2.1.9 and 2.2.2

Pro templates FAQ

Which transmitters can I use with the Pro templates?
All the templates support the FrSky X9D, X9D Plus, X9E, X10 and X12.
Can I use my Q-X7?
The Q-X7 is compatible with the F3F and Wingy templates. Other templates will require modification due to the X7's lack of sliders.
What are the data formats of the templates?
Currently, some templates are in OpenTx 2.1 format, others in 2.2 format. Future versions will be in 2.2 format.
Are the templates compatible with OpenTx 2.2?
All current templates (including sound files) are fully compatible with OpenTx 2.2.1 and later. Note: do not use OpenTx 2.2.0 or release candidate ('RC') versions.
Are the templates compatible with OpenTx 2.1?
Some templates are 2.2 format, and will not work with OpenTx 2.1 - please check the template's download page. You may find a 2.1-compatible version from the template's Version History page. However you will not have all the latest features of the template.

Migrating model data to OpenTx 2.2

If you're running OpenTx 2.1, then at some stage you may wish to migrate to OpenTx 2.2. I won't describe the procedure in detail. Suffice to say that once flashing is complete, all your model data is automatically converted to 2.2 format - this happens the next time you power up your transmitter. There are a couple of potential issues to be aware of:

Custom sounds no longer work after flashing OpenTx 2.2
After flashing your transmitter to OpenTx 2.2, you may find that some setups have 'lost' their custom sounds even though they are present on the SD card. This will be due to a new 6-character limit for filenames introduced in OpenTx 2.2. To fix this, open the template in Companion and go to the Special Functions menu. In the 'Play Track' lines, identify sounds with names of more than 6 characters. In the SD card, shorten the names of these files to 6 characters + '.wav'. Then alter the references in Special Functions to match.
Note: sound files for all current Pro templates satisfy the 6-character limit.
Servo centres shift after flashing OpenTx 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 if PPM Centre has a value other than the default 1500µS. This bug was fixed in OpenTx 2.2; consequently, after migration to 2.2, any channels with non-default PPM Centre will have an unwanted offset. For the Pro templates, the fix is as follows: enter the CAL flight mode, go to the Outputs menu, identify channels with values other than 1500 in the PPM Centre column, then adjust PPM Centre to achieve correct calibration.

Using the Pro templates with non-X9D transmitters

The Pro templates target the X9D, however other transmitters may be used (see download page for supported devices). If using a different transmitter, the template data will be converted when the template file is opened in Companion. There are a couple of things to be aware of:

Knobs or sliders not functioning correctly 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.
A compatibilty warning is displayed in Companion
Starting with version 2.2.2, Companion displays warnings if it finds problems when converting data from one transmitter to another. Not all warnings require user action however (often the conversions will have been performed correctly). In the example below, the source (SRC) of four mixes needs to be checked and if necessary altered to 'S2'.

Companion warnings

Copying all 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, in other words you can migrate from an X9D to an X12S etc. If you're using any of the Pro templates, then see also the section above "Using the Pro templates with non-X9D transmitters".
The recommended OpenTx version for the target is 2.2.2, as Companion will generate useful warnings if problems are encountered. If the source transmitter is running 2.1, then see also the section above "Migrating model data to OpenTx 2.2"
To copy your data to the second transmitter: first, backup the data from your old transmitter ("backup radio to file"). Start Companion and select a profile for the target transmitter. Open the backup; the model data is automatically converted for the target transmitter. Check any conversion issues reported by Companion and fix. Transfer data to the target transmitter ("write models and settings"). Copy all model-specific sound files to the target's SD card. Finally, don't forget to calibrate the sticks.

Other stuff

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.
How do I check for errors in my setup?
If you suspect you made a data entry error, then use Companion's 'Compare models' tool to compare your working version with a known good version.

Current Issues

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

Historical issues

Issues affecting older templates and/or 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.

Queries/feedback

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