OpenTX 2.0 for FrSky Taranis - The Changes

By Andre Bernet - work in progress, last updated 14.04.27 for OpenTX 2.0.0

This document is intended to be a complement to the OpenTX for Taranis manual, to make all changes brought by 2.0 easy to find. It will eventually be merged into a new 2.0 full manual so that new users starting with the 2.0 release can find everything at the same place, but initially most of the users will be existing ones upgrading from r2940.

OpenTX 2.0 for FrSky Taranis - The Changes

Back up your settings!

Upgrading the firmware

Firmware-side changes

Flashing and USB connection

Joystick emulation

General changes

Main views

Radio setup

SD card browser

Model setup

Version screen

Heli setup

Flight modes

Hardware page

Calibration page

Inputs (formerly D/R)

Scripts (LUA)

Back up your settings!

Before we start, please note that OpenTX 2.0 is a major upgrade that adds a lot of new features, but will also require you to change your habits to make use of it. The feedback we’ve had during the beta test period didn’t show that users would lose their bearings, but at the same time these users that jumped in unfinished work are the more “adventurous” type who are less likely to be lost in the first place. So despite all the benefits, it is possible that 2.0 ends up not being for you. For that reason, we strongly recommend you to make a backup of your EEPROM using companion9x’ “Read EEPROM memory to file” command, open that file in companion9x to make sure it’s valid, and keep it safely on your hard drive before going further and doing the upgrade. If you do not have a copy of your current firmware anymore, it would be wise to back that up too using the “Read Flash Memory” command. With this in hand, you can always revert if you don’t feel good.

Upgrading the firmware

To do the upgrade, you will do just as usual and described in the original manual, it can be done with your working companion9x 1.52 setup. The first time you power the radio up after flashing you will be prompted to confirm EEPROM upgrade. Press a key and wait for the end of the process, which will upgrade your old settings to the new format automatically.

PLEASE NOTE: Due to some rather deep changes, a few settings can not be converted and will need to be reconfigured. These include but may not be limited to:

As a general guideline, thoroughly check each of your models for proper operation before flying after the upgrade!

Firmware-side changes

Flashing and USB connection

The first set of changes to the operation will revolve around flashing and PC connection. The image you just wrote to the radio now consists of 2 separate “applications”, the main radio firmware and the bootloader. The firmware runs as usual when you power up the radio normally, and is what you’ll be using most of the time. The bootloader is a minimalist application that is called by holding both horizontal trims inwards while powering the radio up, and that allows special purpose maintenance operations such as:

The “Exit” menu item or a long press of the EXIT key will exit the bootloader and launch the main firmware.

Note that there is no inactivity alarm in the bootloader, so remember to unplug the USB cable and turn the radio off when you’re done!

Joystick emulation

As seen above, settings and SD card access are now done from the bootloader, which means that this feature is not available in the main firmware anymore. So don’t panic if you don’t see any drives in “My computer” when the USB cable is connected when the radio is powered on normally, it’s normal.

The radio will instead be seen as a standard PC joystick, allowing usage with all PC games and simulators that support a standard joystick.

For such usage, you will typically create a new dedicated “model” in which you will turn both RF modules OFF so as to save power and avoid sending out RF unnecessarily.

The mapping is then simple:

So by configuring the mixer how you want you can fully emulate up to 8 proportional axes and 8 buttons, with totally free assignment.

A firmware option selectable in companion (nojoystick) will restore previous behavior if desired, i.e. no joystick function and EEPROM/SD card access with radio firmware running..

General changes

A few items have been renamed for clarity:

A few additions:

Main views

The main views are relatively unchanged. The only differences are:

Radio setup

A few things on the radio setup page:

SD card browser

Model setup

Startup Warning Screen

Version screen

The version numbering system has changed from using an svn revision number to a more “common” version number, starting at 2.0. Both the firmware and the companion will share the same version numbering scheme, making it easier to know if a given combination is compatible or not. Basically, everything that shares the same first 2 numbers (e.g. 2.0.x) is compatible, the last number would relate to bugfixes.

An extra function is now present, a LONG press of the ENTER key will dump a copy of the settings and models memory into the EEPROMS folder of the SD card. The file is named with the date/time of the backup, and can be reloaded from the bootloader if required.

Heli setup

The sources for the CCPM mixer are now the automatically created Ail and Ele Inputs. They should not be reordered or the behavior might be swapped too. Pitch curves should ideally now be entered as a “Pit” Input instead of a virtual channel..

Flight modes

The big change here is that trims now offer more flexibility. There are 4 modes:

The defaults have changed too, all modes now use the same trims by default.

Hardware page

This is a new page that has been added to select your basic hardware configuration. Currently 2 items are supported:

Calibration page

Mostly unchanged except for showing the number of detected detents for multipos switches.

Inputs (formerly D/R)

TODO

Scripts (LUA)

OpenTX 2.0 added support for Lua (current version 5.2.2) user scripts.

Lua is a lightweight multi-paradigm programming language designed as a scripting language. More at Wikipedia

There are two types of Lua scripts used in openTX:

Lua scripts must be placed on SD card in folder /SCRIPTS and have an extension .lua.

Documentation is divided into sub-pages:

Directory structure for LUA

TODO

How to use Lua fields

TODO:

- Menu on limits screen

- Inputs…

- Scripts

- Trims

- Telemetry changes (fas offset, mah etc)

- Other things broken by conversion?

- gvar popups

- Use of the EDGE command which replaces Hshort and Hlong

- What is Inputs and the difference between "[I]Source" and “Source" in mixes