OpenTX 2.2.0 RC17 (N370) Improving your Tx
We are happy to bring you the 15th release candidate of OpenTX 2.2.0, with support for the production version of the FrSky Horus radio!
PLEASE NOTE the following important information before hastily jumping on it:
- This is pre-release software. We’ve done our best to ensure its quality with main focus on the new Horus and X7 platforms, with second priority on all Taranis versions (few changes from 2.1), then the other supported platforms, but we still expect there will be issues. As it is the purpose of a release candidate, we need your feedback to report things we may have missed.
- There is currently no documentation other than this page, so get yourself a good coffee to wake up, and refer to the the great communities for help e.g. openrcforums here, RCGroups and threads like this one. You can pop in our chat room where other users and/or devs may be available.
- Check during companion install that it installs itself in the correct directory, usually you want “Companion 2.2”. A bug that will still show up on this update may cause it to install itself in “Companion 2.1”, potentially overwriting your 2.1 install.
- Companion supports reading and writing Horus firmware when the radio is powered off and then connected to USB, using dfu-util and the libusb drivers installed by Zadig, exactly like for the Taranis. See the “Flashing your Taranis Radio” section in this manual. Companion can back up existing firmware (see note below in known issues) including the stock FrSky one (save as .bin), and can flash the FrSky DFU bootloader so that no other tool and/or driver swapping is needed. You might need to disable the “Check hardware compatibility” checkbox in the flashing dialog.
- SD card contents can be found here. Download the correct archive for your radio type, extract it to the root of an empty SD card and you’ll have all needed files. Please note that all existing OpenTX sound packs won’t work due to changes in the naming strategy, so you’ll likely want to use those that are included in this archive until popular 3rd-party packs are adapted.
- OpenTX does not touch the internal flash of production Horus radios. Its contents do not need to be backed up and are not accessible in any way when OpenTX firmware is loaded.
- There is no bootloader on Horus at this point. The SD card can be accessed while the radio is powered on, providing you selected the “massstorage” firmware option.
- If you are using a beta Horus and are not starting fresh (i.e. you keep your models and settings from a previous OpenTX nightly) you will need to reconfigure pot types on the Radio->Hardware page and recalibrate your sticks and pots.
- Companion installer may try to install itself in the wrong directory, see above.
- The progress bar in companion when reading firmware from a Horus is broken and will reach 100% at only 25% progress. Just wait, the window will close when the process is finished.
A rough view of the changes in OpenTX 2.2 can be found here.
Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type. You need to check “Use OpenTX firmware nightly builds” in companion settings to be able to download firmware, and “Use companion nightly builds” to be notified of further companion release candidate updates.
Horus production version and beta version use different hardware. Companion defaults to production hardware, for beta radios check the “pcbdev” firmware option in the profile settings.
As we are getting closer to 2.2.0 release, we are now focusing on fixing the remaining issues rather than adding new features. As a result, you might see more frequent release of RC until we are ready to release 2.2.0.
If you are working on sound packs or other firmware addons or would like to contribute translations for either the firmware or companion, now is a great time to get ready for 2.2 release. (Translators, you can contact us on rocket.chat if you need assistance)
Changes since 2.2.0 RC16
- Radio : improve CZ translations, fix audio issues [#4831]
- Radio : fix name not displayed when available for last POT [#4840]
- FrSky X7 : fix calibration interruption [#4833]
- FrSky X7 : fix clear line in special function [#4795]
- FrSky X7 : more clear message to differentiate x7 version when external flashing [#4847]
- FrSky radio : fix an issue when both internal_ppm and multimodule where selected [#4822]
- FrSky radio : do not allow selection of telemetry elements in global function [#4810]
- FrSky radio : fix some GPS display issues [#4834]
- FrSky Horus : fix output monitor limits for inverted channels [#4805]
- FrSky Horus : fix emergency mode on max year selection [#4627]
- FrSky Horus : add language specific char handling in text view
- LUA : trying to find the right balance between ram usage and limits [#4827]
- AR9X : fix DS3231 RTC
- 9XPRO: fix multimodule not working
- ARSKY9XRPRO : fix input sources AETR exported as L20-L23
- Companion : fix issue with Horus flashing when startup picture is defined [#4806]
- Companion : fix copy/paste/delete issue in special functions [#4825]
- Companion : fix logical switch name change for Horus JSy [#4841]
- Companion : improve FR translations (merci LapinFou)
- Companion : fix Sky9X settings file handling [#4777]
- Multimodule : fix fallback to Flysky and Spektrum telemetry without MULTI_TELEMETRY
SDCard content for RC17 Note : RC17 uses 2.2v0009. Changes vs 2.2v0008 :
- percent english voice fix
- a few italian plural units
- all languages : silences at the end of files are drasticaly shortened
- Horus : several fixes for BattCheck widgets
OpenTX Companion 2.2.0 RC17 (N370) - Windows Installer If you get an error about “api-ms-win-crt-runtime-I1-1-0.dll missing” install MS VC++ runtime.
OpenTX Companion 2.2.0 RC17 (N370) - Mac OS X Disk Image
OpenTX Companion 2.2.0 RC17 (N370) - Linux DEB Package 64-bit
OpenTX Companion 2.2.0 RC17 (N370) - Ubuntu PPA (Trusty and Yakkety, i386 and amd64)