We are happy to bring you the release version of OpenTX 2.3.0RC1, with support for the production version of the FrSky Xlite-Pro, FrSky X9 Lite, FrSky x10 Express, FrSky X9D+2019 and Jumper T12 radios!

PLEASE NOTE the following important information before hastily jumping on it: Please back up your models and settings before upgrading so that you can go back to your previous version should you not like 2.3 or find issues that make it unsuitable for you. Use the “backup radio to file” companion feature for this to have an exact copy of what was on your radio.

  • As a new major release a new data format has been put in place, existing models and settings will be upgraded keeping things compatible as much as possible, but not everything can be converted. Only OpenTX 2.1 and later settings can be upgraded by the radio, if you currently run an even older firmware version you have to either go through 2.1 first before flashing 2.3, or do the conversion within companion. It is absolutely necessary to go through all your models after the upgrade, check they are operating properly and fix the potential issues before flying or applying motor power.

  • This is a .0 release. A lot of testing has been done by developers and beta testers, but inevitably some issues only pop up with large scale use and particular use cases, if you’re not very adverturous hold off for a few releases until things are well ironed out.

  • The manual has not yet updated to include all Horus documentation/OpenTX 2.3 changes, 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.

  • 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 that where designed for 2.2 or earlier 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.


  • Companion now offers assistance for model conversion from one radio type to another. The transferred models NEED to be completely checked and validation before being used, as some things like switches assignments may not get converted properly. The proper way to transfer models form one radio to the other is to: Select a profile for the destination radio, read the settings from the destination radio, open the source file or read the source radio, drag models onto the destination radio’s window, write destination radio.

Known issues:

  • If you get an “Invalid Language” error when trying to download firmware after upgrading from 2.1 open the profile settings and reselect your radio type, even if it is already correct.
  • 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.

Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type.

New radios
  • X-Lite Pro
  • X9 Lite
  • X10(S) Express
  • X9D+ 2019
  • T12
All radios
  • A new TOOLS screen has been added to radio section. This screen provide a shortcuts to either build in tools, or lua scripts located in /SCRIPTS/TOOLS directory
  • Version screen now allow you to see the options included in your radio firmware
  • Radio logs now logs all switches declared in hardware menu
  • Radio with power button have now adjustment of on/off timing
  • Radio based wizard have been refreshed (Thx LapinFou)
  • When creating a new model, both modules are now defaulted to “OFF”
  • Improve rotary encoder handling on all radios
  • Improve Czeck translations (Thx RCStudio)
  • Improve German translation (Thx SHezinger)
  • Improve Italian translations (Thx mzambrini)
  • Improve Japaneese translations (Thx ku2works)
  • Fix GPS distance calculation on some coordinates
  • RTC Voltage monitoring + alarm (thanks to Mike B)
  • Latency for existing XJT modules (internal or external) has been significantly improved
  • Support for Neuron lines ESC telemetry
  • Support for .frsk firmware files. Those contains identification of target hardware, preventing flashing wrong device with wrong firmware type errors
  • Add RTC battery status
  • Radio with external antenna have now choices ‘per model’ or global settings, with associated updated warnings
  • Taranis now allow up to 40 sensors (up from 32)
  • Support for additional switches for X7 on PAD400 and PAD401
  • Support for X9D REV4a removed (wasn’t compiling since 2.2)
  • ‘full size’ modules available on small size external bay as an option
  • X9E: prevent timer display overflow on top LCD
  • X9E: fix key diagnostic display
  • X9E: all sliders are now added correctly after EEprom reset
  • 128x64: fix trims display
  • 128x64: protect against negative x drawing
  • Horus now allows up to 60 sensors (up from 32)
  • Support for additional switches and pots for X10 and X12
  • X12S internal GPS data are now used only when a decent positionning has been achieved
  • Remplacement Express internal module supported using Companion ‘internalaccess’ option
  • Internal module firmware can now be flashed from OpenTX
  • Add screenshot special function
  • Add R9M flex option to Sky9x
  • Support for Sky9X REVA removed (wasn’t compiling since 2.2)
  • Fix for PPM2 not properly initialised
Radio protocols
  • ACCESS protocol added
  • Support up to 24 channels on ACCESS modules when using ACCESS protocol
  • Spektrum analyser and power meter on compatible ACCESS modules
  • New registration and bind mechanism for ACCESS devices
  • Support for OTA updates for upcoming compatible hardware
  • Add Crossfire telemetry mirror on serial port
  • Add Crossfire telemetry mirror on bluetooth
  • Add iNav vario sensor to Crossfire
  • Support for module Multiprotocol (Thx MRC3742 and PascalLanger)
  • Disable RxNum checks for D8 protocol
  • Mixer to pulse synchronisation improved
  • Display FlySky volts as signed values (Thx CapnBry)
  • Fix TIMEHOUR handling on 128x64 screens
  • Telem 1 to (40/60) items added
  • Lua mix scripts outputs added
  • Fix DIY first ID to 0x5100
  • Introduction of virtual navigation keys
  • Added string type to Horus widget
  • global functions scripts do no run anymore if global functions are disabled in model config
  • GPS data now have a delay attribute
  • “chdir” function added
  • Fix 1bit bitmap draw on 128x64 displays
  • Multimodule, Crossfire and luac options are included by default in all firmware
  • Fix for Negative GVAR precision (Thx Elecpower)
  • Add receiver number to model list (Thx Elecpower)
  • Add Japaneese translation (Thx Ku2works)
  • Improve french translation (Thx LapinFou)
  • Fix Companion wizard
  • Companion now informs when radio are not currently available

For more details, see here.

SDCard content for 2.3.0RC1

Note: 2.3.0RC1 uses 2.3v0021. Changes vs 2.2:

  • Several units have been added
  • FrSky Neuron SBEC configuration script added
  • Lots of translations improvement
  • Fix Horus wizard when no motor is chosen
  • Improve Horus Batt wideget (Thx shmuely)
  • Add Horus Timer2 widget (Thx shmuely)
  • Some scripts have been moved to TOOLS

OpenTX Companion 2.3.0RC1 - Windows Installer If you get an error about “api-ms-win-crt-runtime-I1-1-0.dll missing” install MS VC++ runtime.

If you’re unable to run Companion 2.3. after install, try importing this registry fix to avoid companion importing settings from a previous version. Note this clears any existing Companion 2.3 settings.

OpenTX Companion 2.3.0RC1 - Mac OS X Disk Image

OpenTX Companion 2.3.0RC1 - Linux DEB Package 64-bit


11 September 2019