Tuesday, 31 January 2017

Preparing your setups for OpenTx 2.2 RC10

The OpenTx developers have been making great progress with 2.2. The latest build is able to open .eepes created in OpenTx 2.1, and convert them to OpenTx 2.2 format. Even better, they can be re-targeted to the Horus - great news for those wishing to migrate their setups to the new transmitter.

With this in mind, I've embarked on modding my E-Soar Plus for operation with 2.2. The resulting .eepe file remains in 2.1 format to be compatible with the largest range of systems.


Changes in OpenTx 2.2

Here are some of the key changes in OpenTx 2.2 affecting translation of older .eepes.

Shorter object names

The maximum length of some object names has been reduced in OpenTx 2.2:
  • GVAR names - reduced from 6 to 3 characters max (Horus and Taranis)
  • Curve names - reduced from 6 to 3 characters (Horus and Taranis)
  • Mixer line names - reduced from 8 to 6 characters max (Horus only, no change for Taranis).
If a setup is opened with names which are too long, they are silently truncated. When planning a setup in 2.1 with a view to migrating to 2.2, it's worth making the start of each name meaningful.

Shorter filenames

Filenames of user-specified sound files, as well as script files, are limited to 6 characters + extension. If you reference longer filenames in Special Functions then these will need to be altered.

Control mapping from Taranis to Horus

When importing Taranis .eepes into the Horus, some controls don't map as expected:

S2 → 6P
LS → L1
RS →L2

After import, check for any references to 6P, L1 or L2 and correct as necessary.

Working with Companion RC10

Companion RC10 does not support drag and drop of models from one eeprom to another. However cut and paste via Ctrl+C, Ctrl+V is supported. To paste into a new model, create a dummy model in the target eeprom, and paste into that.

No comments: