View source for KAVAN V20 + ETHOS™ - User manual

<languages/>
<translate>
==Main views== <!--T:1-->

<!--T:2-->
The operating system '''ETHOS™''' allows users to fully customize the Main views. By default, only basic information (see below) is displayed. You can easily edit or add custom widgets. You can set up to 8 Main views. The Main views have the same top and bottom bars. However, you can set the main view to fullscreen. Customization details are in the '''Configure screens''' section.

<!--T:3-->
If you have any questions about the V20 transmitter and its operation, please contact the technical and service staff at KAVAN Europe s.r.o. by e-mail ('''info@kavanrc.com''' for general technical information, '''service@kavanrc.com''' for service) or by phone ('''+420 466 260 133''' for general technical information, '''+420 463 358 700''' for service), during working hours 8 am–4 pm CET, Monday to Friday).

<!--T:4-->
===Top bar===
The top bar shows the name of the model and set flight mode (if configured). The icons on the right show the general overview of the transmitter parameters:

<!--T:5-->
* Data logging status
* Trainer mode icon
* RSSI 2.4G (FSK and Lora)
* Speaker volume
* Transmitter battery status

<!--T:6-->
Touching the speaker and battery icons will bring up the relevant '''General''' ('''Audio''' etc.) and '''Battery''' control panels.

<!--T:7-->
===Bottom bar===
The bottom bar has four tabs for accessing the advanced functions, i.e. '''Home''', '''Model Setup''', '''Configure Screens''', and '''System Setup'''. The system time is displayed on the right. Touching the time will open the '''Date & Time''' settings.

<!--T:8-->
===Widgets===
The middle area of the Main Views consists of widgets which may be configured to display images, timers, telemetry data, radio values etc. The default main screen has a widget on the left for a model image and three widgets for timers, as well as displaying the trims and pots. The widgets are user-configurable to display other information. Once multiple screens have been configured, they can be accessed using a touch swipe gesture or navigation controls.

<!--T:9-->
Please refer to the Configure Screens section for more details.

<!--T:10-->
==User interface and navigation==
The V20 transmitter has a touchscreen display, making the user interface very intuitive and simple to control. Touching the
'''Model Setup''' (Aircraft icon), '''Configure Screens''' (Multiple Screens icon), and '''System Setup''' (Gear icon) tabs to go directly to these functions. See the following sections of the manual for their description. They can also be accessed using the '''[MODEL]''', '''[DISPLAY]''', and '''[SYSTEM]''' buttons.

<!--T:11-->
* Press and hold the '''[BACK]''' key to return to the home screen from any submenu.
* Press system time on the right side of the bottom bar to access the '''Date and time''' settings section.
* Press the speaker or battery icon in the top bar to bring up the respective '''Sound and Vibration''' or '''Battery''' control panels.

<!--T:12-->
===Reset menu===
Long press the '''[ENT]''' button to display the Reset menu, where you can reset telemetry, timers, or both by selecting "Reset Flight". After pressing "Reset Flight", the pre-flight checks will be performed.

<!--T:13-->
===Editing controls===
====Virtual keyboard====
A touch-sensitive keyboard is available for typing into text fields.
 
* Press any text field (or press the '''[ENT]''' button) to bring up the keyboard.
* Press the '''?123''' or '''abc''' button to switch between the conventional and numeric keypad.

<!--T:14-->
===Number values===
When a numeric value is pressed, a dialogue box appears with buttons to set the value to the lowest (Min), default (Default) or highest (Max) value, as well as "plus" and "minus" buttons to increase or decrease the value precisely. Additionally, a slider across the bottom allows you to adjust the output of the one-click rotary encoder to a range from 1:1 to fine on the left and coarse on the right. The slider value can be set by rotating the multifunctional knob while holding it pressed.

<!--T:15-->
=== Advanced options ===
ETHOS™ has an extensive range of advanced settings. For most numeric fields, long press the '''[ENTER]''' button to display the Advanced options menu.

<!--T:16-->
Open the Advanced options field by the hidden menu (hamburger) symbol in the upper left corner of the field.

<!--T:17-->
==== Value options ====
The '''Value options''' dialogue displays the parameter you are currently setting. For example, you can set the Rates value to minimum, maximum, or specify a source (such as a potentiometer). By designating a potentiometer as the source, you can control the value of the parameter on the fly by turning the potentiometer.

<!--T:18-->
If you click on a value field that has already been changed to "Source", a dialogue will appear allowing you to convert the current source value to a fixed value. Press "Options" to display the options for setting the source:

<!--T:19-->
===== Invert =====
The Invert function allows you to negate/invert a source, like a switch position. For example, instead of the SA switch being active in the "Up" position, it will be active in the "Down" position.

<!--T:20-->
===== Edge =====
You can select the Edge option if you require a one-time action when a source goes from False to True or from True to False. The action is only triggered by the change of states, not by the True or False state.

<!--T:21-->
===== Ignore trainer input =====
For logical switch sources, this option can be set to ignore sources coming from the input of the student's transmitter. A typical use case is when a logical switch is configured to detect the movement of the teacher's transmitter sticks (e.g., the elevator control) to allow immediate action if something goes wrong. This option is needed to prevent the logic switch from being triggered by the student's stick inputs.

<!--T:22-->
===== Sensor options =====
In the Telemetry source settings dialogue box, you can find the Invert, Maximum and Minimum values. Some sensors also offer other specific settings.

== USB connection modes == <!--T:23-->

<!--T:24-->
=== Power OFF mode ===
Connecting the transmitter while powered OFF to a PC via a USB cable is the DFU (Device Firmware Update) mode for flashing the bootloader.

<!--T:25-->
=== Bootloader mode ===
The transmitter is placed in the bootloader mode by switching on the radio with the '''[ENTER]''' key held down. The status message "Bootloader" will pop up on the screen.

<!--T:26-->
The transmitter can then be connected to a PC via a USB data cable. The status message will change to ‘USB Plugged’, and the PC should display two external drives connected. The first is for the V20 flash memory, and the second is the content of the MicroSD card.

<!--T:27-->
This mode is used for reading and writing files on SD card and/or the V20 flash memory.

<!--T:28-->
=== Power ON mode ===
If the transmitter is switched on adn connected to the computer via the USB data cable, a dialogue box with the following options will appear:

<!--T:29-->
* '''Joystick''': in this mode the transmitter can be configured to control RC simulators.
* '''ETHOS Suite''': in this mode, the transmitter is in "ETHOS Mode" to communicate with the ETHOS Suite. For information on Ethos mode, please refer to the Ethos Suite section.
* '''Serial''': In this mode, Lua debug traces, if present, are sent via USB. The baud rate is 115200 bps. A suitable Windows virtual COM port driver is STSW-STM32102.

<!--T:980-->
== Emergency mode ==
Emergency mode is the transmitter's response to an unexpected event, such as a watchdog timer interrupt. A watchdog is a timer that is constantly restarted by various parts of the ETHOS system. If a malfunction of any kind prevents the watchdog timer from restarting, it will time out and a hardware reset of the transmitter will occur. In the emergency mode, the transmitter reboots extremely quickly, without any of the normal startup checks, to regain control of the model as quickly as possible. There is no access to the microSD card in safe mode.

<!--T:31-->
Safe mode provides only the basic functions to control the model. The screen will turn OFF and the Emergency Mode message will be displayed accompanied by a 300ms beep repeated every 3 seconds. Voice alerts, script execution, logging, etc. will stop working. When the Emergency Mode is activated, immediately land/stop your model.

<!--T:32-->
The most common cause of emergency mode triggering is a MicroSD card failure.

<!--T:33-->
== System setup ==
System setup is used to configure the hardware parts of the transmitter system that are common to all models. The settings can be accessed by selecting the Devices tab at the bottom of the screen.

<!--T:34-->
Note that the setting that determines whether to use an internal or external RF module is model specific and is therefore set in the "RF System" section of the model settings.

=== Overview === <!--T:35-->

<!--T:36-->
==== File manager ====
Manage files and access the flash firmware to the TW-ISRM, external S.Port, OTA and external modules.

<!--T:37-->
==== Alerts ====
Configure alerts for silent mode, battery status, and idle status.

<!--T:38-->
==== Date and time ====
Configure the system time and display options.

<!--T:39-->
==== General ====
Configure menu style, system language, and LCD display attributes such as brightness and backlight, as well as Audio, Vario, and Haptics sound modes.

<!--T:40-->
==== Battery ====
Configure battery management settings.

<!--T:41-->
==== Hardware ====
Check the hardware physical input devices and calibrating analogue devices and gyroscopes. Also allows changing switch type definitions.

<!--T:42-->
==== Sticks ====
Set the mode and default channel order. The 4 control channels can also be renamed.

<!--T:43-->
==== Wireless ====
Configure the Bluetooth module.

<!--T:44-->
==== Info ====
System information about firmware version, gimbal type and RF modules.

<!--T:45-->
=== File manager ===
The File Manager is for managing files and access to flash firmware to the TW-ISRM, external S.Port, OTA and external modules.

<!--T:46-->
Note: When updating the system firmware, the files in the flash drive and SD card may also need updating.

<!--T:47-->
==== audio/ ====
USB drive path: (MicroSD drive letter)/audio/

<!--T:48-->
This folder is for user audio files that can be played using the special "Play track" function. See '''Model''' / '''Special Functions'''. The format should be 16kHz or 32kHz PCM linear 16bit or alaw (EU) 8bit or mulaw (US) 8bit.

<!--T:49-->
==== audio/en/system ====
USB drive path: (MicroSD drive letter)/audio/en/system

<!--T:50-->
This folder is for system audio files:

<!--T:51-->
* hello.wav - Welcome greeting "Welcome to ETHOS"
* bye.wav - Goodbye is not included by default for now, but you can add your own, in .wav format.

<!--T:52-->
Press '''[audio]''' to view the contents of the folder. Press the .wav file and select Play to listen to it. Files can also be copied, moved, or deleted.

<!--T:53-->
==== bitmaps/models/ ====
USB drive path: (MicroSD drive letter)/bitmaps/models/ (before Ethos 1.2.6 this folder was bitmaps/user)

<!--T:54-->
This folder is for images of user models. The recommended image format for reducing the computational load of the V20 embedded microcontroller is:

<!--T:55-->
* 32-bit BMP format with a size of 300×280 px
* 8 bits per color channel
* Alpha channel (transparency)

<!--T:56-->
Rules for naming image files:

<!--T:57-->
* Use only the characters A–Z, a–z, 0–9, ( ) ! - _ @ # ; [ ] + = and space.
* The name must not contain more than 11 characters plus 4 characters for the file name extension. If the name is longer than 11 characters, it will appear in the SD Card File Manager, but will not appear in the model image selection interface.

<!--T:58-->
==== Image conversion tools ====
There are several useful image conversion tools available:

<!--T:59-->
* Windows-based - <nowiki>https://github.com/Ceeb182/ConvertToETHOSBMPformat</nowiki> (this tool also applies file naming rules)
* Web-based - <nowiki>https://ethosbmp.hobby4life.nl/</nowiki>

<!--T:60-->
==== Firmware ====
Here you can find firmware updates for the internal V20 TW-ISRM RF module, external modules and other devices such as receivers etc. From here, they can then be flashed via the external S.Port on the transmitter or wirelessly via OTA (Over The Air). The new firmware needs to be copied to the '''Firmware''' folder after putting the V20 into Bootloader mode and connecting to a PC via the USB.

<!--T:61-->
Press the '''Firmware''' folder to view the firmware files copied into this folder. Then press the '''Flash''' option in the pop-up dialogue.

<!--T:62-->
Files can also be copied, moved or deleted.

<!--T:63-->
==== Logs ====
Data logs are stored here.

<!--T:64-->
USB drive path: (MicroSD drive letter)/Logs/models/

<!--T:65-->
This is where the model files are stored. These files cannot be edited by the user, but can be backed up or shared from here. It uses the model names. For example, a model named "Swift" will have the file name "Swift.bin". If there is more than one "Swift" model, the others will be named "Swift01.bin" and so on.

<!--T:66-->
When editing model names on the Edit Model screen, the model file name (.bin) will also change. The model file name will be listed in all lower case (the actual model name with upper and lower case characters is stored inside the bin). Not all characters are supported for the bin name of the model file, so it may not exactly match the model name.

<!--T:67-->
USB drive path: (drive letter)/models/

<!--T:68-->
There are subfolders for each user-created model category folder.

<!--T:69-->
==== screenshots/ ====
USB drive path: (MicroSD drive letter)/screenshots/

<!--T:70-->
This is where screenshots taken with the '''Screenshot''' feature are stored. See '''Model''' / '''Special Features'''.

<!--T:71-->
==== scripts/ ====
USB drive path: (MicroSD drive letter)/scripts/

<!--T:72-->
Lua scripts are stored here. The scripts can be organized into individual folders.

<!--T:73-->
 '''Caution:''' Lua scripts increase the start time of the transmitter. If they are implemented correctly, the delay shouldn't be noticeable, but if not, the delay may be very significant, at worst indefinite.

<!--T:952-->
===== Scripts for external modules =====
Each third-party external module has its own Lua file and should be stored in its own folder.

<!--T:75-->
* scripts/multi
* scripts/elrs
* scripts/ghost
* scripts/crossfire

<!--T:953-->
==== radio.bin ====
USB drive path: (MicroSD drive letter)/radio.bin

<!--T:77-->
USB drive path: (MicroSD drive letter)/firmware.bin

<!--T:78-->
This file is created by the V20 when it is first used. It stores the  system settings. It should be backed up with the '''models''' folder before upgrading the firmware so that a downgrade to an older version can be performed if necessary.

<!--T:79-->
When updating the transmitter firmware, the '''firmware.bin''' file should be stored in the root folder of the MicroSD card. Once the new '''firmware.bin''' file is saved, the update will be automatically uploaded to the V20 when it is disconnected from the computer.
 '''''Note:''' it may also be necessary to update the contents of the SD card and the radio's flash drive at the same time.''

=== Alerts === <!--T:80-->

<!--T:81-->
==== Silent mode ====
At startup, a silent mode alert is displayed when the silent mode check is enabled and the sound is set to '''Silent Mode''' in '''System'''/'''General''' settings.

<!--T:82-->
==== Main voltage ====
If the main battery voltage check is turned on and the transmitter battery voltage is below the threshold set in "'''Low Voltage'''" in '''System'''/'''Battery''', the message "'''Radio battery is low'''" is displayed.

<!--T:981-->
==== RTC voltage ====
RTC battery is providing the energy for the internal Real Time Clock circuit. The "'''RTC Battery is Low'''" message is displayed when the RTC battery voltage check is enabled and the RTC button battery is below 2.5 V, the default RTC battery threshold. It can be turned OFF until the RTC battery is replaced, but should not be turned OFF indefinitely. Real time is used in data logging and invalid time will cause difficulty in reading the logs, especially in distinguishing flight sessions.

<!--T:982-->
==== Sensor conflict warning ====
Sensor conflict detection can be disabled. This should only be necessary if you have sensors that do not meet the S.Port specification.

<!--T:85-->
==== Inactivity ====
If the radio is not in use for more than a period of "inactivity", a voice alert "'''No activity for a long time'''" will be displayed, as well as a haptic alert if the speaker volume is low. The default value is 10 minutes.

<!--T:86-->
=== Date and time ===
The Date and Time settings are:

<!--T:87-->
==== 24 hour time ====
The clock is displayed in 24-hour format when switched on.

<!--T:88-->
==== Display seconds ====
The clock will display seconds if enabled.

<!--T:89-->
==== Date ====
Set the current date for use in logs.

<!--T:90-->
==== Time ====
Set the current time for use in logs.

<!--T:91-->
==== Time zone ====
Allows configuration of the user's time zone.

<!--T:92-->
==== Adjust RTC speed ====
The real time clock can be calibrated to compensate for any clock drift, up to 41 seconds per day.

<!--T:93-->
To calibrate, determine how many seconds your clock gains or loses in 24 hours. Set the calibration value to twelve times this number of seconds, so it will be negative if your clock is running faster, and positive if it is running slower. You can then check to see if your clock is accurate and adjust the calibration value slightly for maximum accuracy. The actual calibration value can be set to -500 to +500.

<!--T:94-->
==== Auto adjust from GPS ====
When enabled, the time and date will be automatically set from remote GPS sensor data.

<!--T:983-->
=== General ===
The following can be configured here:

<!--T:96-->
* The language of the ETHOS user interface and audio
* LCD screen attributes
* Audio modes and volume

==== Language ==== <!--T:97-->

<!--T:98-->
===== User interface =====
The following languages are supported for the display menus:

<!--T:99-->
* English
* German
* Czech
* Spanish
* French
* Chinese
* Hebrew
* Italian
* Dutch
* Norway
* Polish
* Portuguese

<!--T:100-->
===== Audio =====
Ensure that you have installed the corresponding voice pack in your SD card to ensure the appropriate voice output.

<!--T:101-->
===== Keyboard =====
Allows selection between QWERTY, QWERTZ and AZERTY virtual keyboard layouts.

<!--T:102-->
==== Display attributes ====
The LCD Display attributes can be configured here:

<!--T:103-->
===== Brightness =====
Use the slider to control the screen brightness, from left to right to set brightness from dark to bright. Long press [ENT] brings up options to use a source, or set it to minimum or maximum.

<!--T:104-->
===== Pot option =====
Press „'''Use a source'''“ and select a potentiometer to use for controlling the brightness. 

<!--T:105-->
===== Wake up =====
The screen backlight can be woken from the sleep state according to the settings:

<!--T:106-->
* '''Always on:''' the backlight is always on.

<!--T:107-->
* '''Sticks:''' the backlight turns on when sticks or buttons are operated.

<!--T:108-->
* '''Switches:''' the backlight turns on when switches or buttons are operated.

<!--T:109-->
* '''Gyro:''' the backlight turns on when you tilt the transmitter or when buttons are operated.
 '''Note:''' More than one option may be enabled.

<!--T:110-->
===== Sleep =====
Duration of the inactivity before the backlight turns OFF.

<!--T:111-->
===== Sleep mode brightness =====
Use the slider to control the screen brightness during sleep mode, from left to right to set brightness from dark to bright.

<!--T:984-->
===== Dark mode =====
Select light or dark user interface theme.

<!--T:113-->
===== Highlight colour =====
Select the highlights colour of the user interface. Default is yellow (#F8B038).

<!--T:985-->
==== Audio settings ====
The audio settings are:

<!--T:115-->
===== Main volume =====
Use the slider to control the audio volume. Long press '''[ENTER]''' allows a pot to be used. Beeps during adjustment assist in judging the volume.

===== Audio mode ===== <!--T:116-->

<!--T:954-->
* '''Silent:''' No audio. Note that there will be an Alert given at startup if the Silent Mode Check in '''System''' / '''Alerts''' is ON..

<!--T:117-->
* '''Alarms only:''' Only Alarms will be output on audio.

<!--T:118-->
* '''Default:''' Sounds are on.

<!--T:119-->
* '''Often:''' There will additionally be error beeps when attempting to exceed the maximum or minimum value on editable numbers.

<!--T:120-->
* '''Always:''' In addition to the sounds in 'Often', there will also be beeps when the menu is navigated.

<!--T:121-->
===== Vario =====
The audio characteristics of Vario tones can be configured here.

<!--T:122-->
* '''Volume:''' Relative tone volume of the vario.

<!--T:123-->
* '''Pitch zero:''' The pitch at zero climb rate.

<!--T:124-->
* '''Tón max:''' The pitch at maximum climb rate.

<!--T:125-->
* '''Repeat:''' Delay between beeps at Pitch zero.

<!--T:955-->
For more parameters of the Vario system, see '''Speed sensor''' in the '''Telemetry''' section.

===== Haptic ===== <!--T:126-->

<!--T:127-->
* '''Strength:''' Use the slider to control the strength of the vibrations.

<!--T:956-->
* '''Mode:''' Similar to the Audio mode above.

==== Top toolbar ==== <!--T:128-->

<!--T:130-->
===== Digital voltage =====
The charge status indicator can be changed from the default mode to display the digital value of the transmitter battery voltage.

<!--T:131-->
===== Digital RSSI =====
Similarly, the RSSI status can be changed from a bar display to a digital value.

<!--T:132-->
=== Battery ===
The Battery section is used to set the clock battery and transmitter battery alarm thresholds.

<!--T:133-->
==== Main voltage ====
This is the nominal voltage of the battery. The default value is 8.4 V for a charged 2S LiPo battery.

<!--T:134-->
==== Low voltage ====
This is the low threshold of the transmitter battery voltage at which the alarm will sound. The default value is 7.2 V.

<!--T:957-->
Varovná hláška „Baterie rádia je slabá“ se zobrazí, když je v nabídce '''Systém''' / '''Upozornění''' zapnuta kontrola hlavní baterie a napětí vysílačového akumulátoru je nižší než nastavená prahová hodnotoa.

<!--T:135-->
The warning message "Radio battery is low" is displayed when the Main Battery Check is active in the '''System''' / '''Alerts''' menu and the voltage of the transmitter battery is below the set threshold.
 '''''Caution:''''' ''If this warning appears, we recommend that you terminate the flight immediately and charge the transmitter battery!''
 
 ''If the voltage of the transmitter battery drops to 6.0 V, the transmitter will switch OFF without further warning to protect the transmitter battery (2S LiPo - 2×3.0 V) and you will not be able to operate the model!''

<!--T:136-->
==== Display voltage range ====
These settings set the range of the battery indicator in the top right corner of the screen. The default range limits for the LiPo battery are 6.4 and 8.4 V. Many pilots increase the lower limit to trigger the low transmitter battery voltage warning sooner to prevent battery over-discharge.

<!--T:137-->
If the battery is replaced with a different type, the limits must be set accordingly.

<!--T:958-->
==== RTC voltage ====
Displays the RTC (Real Time Clock) battery voltage in the transmitter. For a new battery, the voltage is 3.0 V, if the voltage is less than 2.7 V, replace the battery inside the radio to ensure proper clock operation. If the voltage drops below 2.5 V, an alert will be displayed, see section '''Alerts''' / '''RTC Battery Check'''.

=== Hardware === <!--T:959-->

<!--T:139-->
The Hardware section is used to test all inputs, perform analogue and gyro calibration and set switch types.

<!--T:140-->
==== Hardware check ====
The hardware check allows you to check the functionality of all inputs.

<!--T:986-->
==== Analogs calibration ====
The calibration of the analogue elements of the transmitter is done so that the transmitter knows exactly in which position the control element (gimbals, rotary and sliding potentiometers) is located. The calibration is always performed at the first start-up. It must be done when replacing the gimbals or any of the potentiometers.

<!--T:142-->
==== Gyro calibration ====
Calibration of the gyro must be performed to ensure that the gyro sensor outputs respond correctly to the transmitter tilt. This is done automatically on first start-up. For example, the transmitter position "horizontal" is the angle at which you normally hold the radio.

<!--T:987-->
==== Analogs filter ====
This setting can be used to enable/disable the analogue-to-digital converter (ADC) filter. The default value is ON. This may improve a possible small inaccuracy around the centre position of the gimbal. This is a global setting on this Hardware page. In the '''Edit Model''' section, there is a model-specific option in the '''Analogs Filter''' setting.

<!--T:988-->
==== Pots/sliders settings ====
The pots and sliders can be given custom names here.

==== Switches settings ==== <!--T:960-->

===== Switch middle detect delay ===== <!--T:145-->

<!--T:146-->
This setting ensures that the switch middle position on three way switches is not detected when the switch is flipped from the up to the down position in one movement, and vice versa. It should only be detected when the switch stops in the middle position. The default has been changed to 0ms to suit the FrSky stabilized receivers when detecting '''Self Check''' on CH12.

<!--T:147-->
Switches SA to SJ may be defined as:

<!--T:148-->
* None
* Momentary
* 2-position
* 3-position

<!--T:149-->
This allows for switches to be swapped over, for example the momentary switch SH could be swapped over with the 2 position switch SF. Note that it may not be possible to replace a momentary or 2 position with a 3 position switch if the radio wiring does not allow for it.

<!--T:150-->
Switches may also be renamed from the default names SA through SJ to custom names. Note that these names will be global across all models.

<!--T:989-->
==== Home Keymap ====
Buttons '''[SYSTEM]''', '''[MODEL]''' and '''[DISPLAY]''' can be re-assigned to suit the user.

<!--T:152-->
===== [SYSTEM] and [MODEL] buttons =====
For the '''[SYSTEM]''' and '''[MODEL]''' buttons only the long-press options may be re-assigned to any '''Model''' or '''System''' page or the Configure Screens page. A short press calls either the '''System''' or '''Model''' section respectively.

<!--T:153-->
===== [DISPLAY] button =====
For the '''[DISPLAY]''' key both short and long press options may be re-assigned to any '''Model''' or '''System''' page or the '''Configure Screens''' page.

<!--T:990-->
==== ADC value inspector ====
Shows the analogue to digital conversion (ADC) values for the analog inputs read by the CPU.

<!--T:155-->
# Left gimbal horizontal
# Left gimbal vertical
# Right gimbal vertical
# Right gimbal horizontal
# Pot 1
# Pot 2
# Middle slider pot
# Left rotary slider pot
# Right rotary slider pot

<!--T:156-->
=== Sticks ===
Select your preferred stick mode. Mode 1 has throttle and aileron on the right stick, and elevator and rudder on the left. Mode 2 has throttle and rudder on the left stick, and aileron and elevator on the right.

<!--T:157-->
By default the sticks are named as listed above for the industry standard stick modes. They may be renamed as desired.

<!--T:158-->
==== Channel order ====
The Channel Order defines the order in which the four stick inputs are assigned to channels in the mixer when a new model is created by the wizards. The default order is '''AETR'''. If there are more than one of each type of surface, they will be grouped unless the first four channels are fixed, see below. For example, for 2 ailerons the channel order will be '''AAETR'''.

<!--T:159-->
==== First four channels fixed ====
When this option is enabled, then channel grouping will not occur on the first four channels. If the channel order is '''AETR''', then the wizard will create a model suited to the SRx stabilized receivers. For example, a model with 2 Ailerons, 1 Elevator, 1 Motor, 1 Rudder and 2 Flaps will be created with a channel order of '''AETRAFF'''. If this option is not enabled, the channel order would be '''AAETRFF'''.

<!--T:160-->
=== Wireless ===
Touch the '''Bluetooth Mode''' to bring up a dialog listing the Bluetooth options.

<!--T:161-->
==== Bluetooth mode ====
The V20 Bluetooth module can operate in telemetry or trainer modes.

<!--T:162-->
===== Telemety =====
In telemetry mode, the radio can work with the '''FrSky FreeLink''' app and display telemetry data on your mobile phone. The FreeLink app can also be used to configure other devices, e.g. stabilised receivers.

<!--T:163-->
===== Trainer =====
In Trainer mode, the radio can be operated in Master or Slave mode to achieve the Trainer function wirelessly. See the '''Model''' / '''Trainer''' section to configure the transmitter as Master or Slave for the currently selected model.

<!--T:164-->
===== Local name =====
This is the local Bluetooth name that appears on connected devices. The default name is '''FrSkyBT''', but it can be modified here.

<!--T:165-->
===== Local address =====
This is the local address of the Bluetooth module.

<!--T:166-->
===== Dist address =====
When a Bluetooth device is found and connected, the Bluetooth address of the remote device is displayed here.

<!--T:167-->
===== Search devices =====
The '''[SELECT]''' button of the device will be available when the Teacher/Pupil mode is in Teacher mode (see '''Model''' / '''Trainer''' section).

<!--T:168-->
Tap on '''Search Devices''' to put the radio into Bluetooth search mode.

<!--T:169-->
The found devices are displayed in a pop-up window asking you to select a device. Select the address of the Bluetooth transmitter to be used as a slave.

<!--T:170-->
=== Info ===
The Info page displays information about the system firmware, the type of gimbal, the firmware version of the internal module, the ACCESS receiver firmware, and information about the external module.

<!--T:171-->
==== Firmware ====
ETHOS firmware and type of the transmitter (V20).

<!--T:172-->
==== Firmware version ====
Current firmware version and type.

<!--T:173-->
==== Date ====
Date and time of the firmware version.

<!--T:174-->
==== Sticks ====
Installed version of Hall sensor gimbal driver. ADC is for analogue-digital converter.

<!--T:175-->
==== Internal module ====
Details of the internal RF module, including hardware and firmware versions.

<!--T:176-->
==== Receivers ====
Details of the bound receivers are listed after the internal module. If the redundant receiver is bound to the same slot as the main receiver, the display will show details of both receivers alternately.

<!--T:177-->
==== External module ====
Details of the external RF module (if fitted), including hardware and firmware version if ACCESS protocol is available.

<!--T:178-->
Multimodules aren't displayed.

<!--T:961-->
== Model setup ==
The Model setup menu is used to configure each model’s specific setup. It is accessed by selecting the Airplane tab along the bottom of the Home screen. Conversely, settings that are common to all models are performed in the '''System''' menu, which is accessed by selecting the Gear tab instead (please refer to the '''System''' section). 

=== Overview === <!--T:179-->

<!--T:181-->
==== Model select ====
The '''Model Select''' option is used to create, select, add, clone, or delete models. It is also used to create and manage user-specific model category folders.

<!--T:991-->
==== Edit model ====
The '''Edit model''' option is used to edit the basic parameters for the model as set up by the wizard, and is mainly used to edit the model name or picture. It is also used to configure the function switches, which are model-specific.

<!--T:183-->
==== Flight modes ====
Flight modes allow models to be set up for switch selectable specific tasks or flight behaviour. For example, gliders may be set up to have flight modes such as Launch, Cruise, Speed and Thermal. Power planes may have flight modes for Normal flying, Take OFF and Landing. Helicopters have modes such as Normal for spool up and take OFF/landing, Idle Up 1 for aerobatic flying, and Idle Up 2 for 3D aerobatics etc.

<!--T:184-->
==== Mixer ====
The '''Mixer''' section is where the model’s control functions are configured. It allows any of the many sources of input to be combined as desired and mapped to any of the output channels. This section also allows the source to be conditioned by defining weights/rates and offsets, adding curves (eg Expo). The mix can be made subject to a switch and/or flight modes, and a slow function to be added.

<!--T:185-->
==== Outputs ====
The '''Outputs''' section is the interface between the setup "logic" and the real world with servos, linkages and control surfaces as well as actuators and transducers. In the Mixer we have set up what we want our different controls to do. This section allows these pure logical outputs to be adapted to the mechanical characteristics of the model. This is where we configure minimum and maximum throws, servo or channel reverse, and adjust the servo or channel center point using the PPM center adjustment, or add an offset using subtrim. We can also define a curve to correct any real world response issues. For example, a curve can be used to ensure that left and right flaps track accurately.

<!--T:186-->
==== Timers ====
Timers are used to set the three available timers.

<!--T:187-->
==== Trims ====
The '''Trims''' section allows you to set trim modes, disable trim, enable extended trim, or enable independent trim for each of the 4 trim switches.

<!--T:188-->
==== RF System ====
This section is used to configure the Owner Registration ID ('''RID'''), and the internal and/or external RF modules. This is also where receiver binding takes place, and receiver options are configured. The RID is an 8 character string that contains a unique random code, which can be changed if desired. This ID becomes the Owner Registration ID ('''UID''') when registering a receiver. Enter the same code in the Owner ID field of your other transmitters you want to use the Smart Share feature with them. This must be done before creating the model you want to use it on.

<!--T:189-->
==== Telemetry ====
Telemetry is used to transmit information from the model back to the transmitter. This information can be quite extensive and includes RSSI (receiver signal strength) and link quality, various voltages, currents and any other sensor outputs such as GPS position, altitude etc. Note that the telemetry screens are set as the main display in the '''Configure Screens''' section.

<!--T:190-->
==== Checklist ====
The Checklist section is used to define startup alerts for things like initial throttle position, whether failsafe is configured, pot and slider positions, and initial switch positions.

<!--T:191-->
==== Logical switches ====
Logic switches are user programmed virtual switches. They aren’t physical switches that you flip from one position to another, however they can be used as program triggers in the same way as any physical switch. They are turned ON and OFF by evaluating the conditions of the programming. They may use a variety of inputs such as physical switches, other logical switches, and other sources such as telemetry values, channel values, timer values, or Global Variables. They can even use values returned by a LUA model script.

<!--T:192-->
==== Special functions ====
This is where switches can be used to trigger special functions such as trainer mode, soundtrack playback, speech output of variables, data logging etc. '''Special Functions''' are used to configure model specific functions.

<!--T:193-->
==== Curves ====
Custom curves can be used in input formatting, in the mixers or in the outputs. There are 50 curves available, and can be of several types (between 2 and 21 point, with either fixed or user-definable x-coordinates). In the Mixer a typical application is using an Expo curve to soften the response around midstick. A curve may also be used to smooth a flap to elevator compensation mix so that the aircraft does not 'balloon up' when flaps are applied. In the Outputs a balancing curve may be used to ensure accurate tracking of the left and right flaps.

<!--T:194-->
==== Trainer ====
The '''Trainer''' section is used to set the radio as a Master or Slave in a trainer setup. The trainer link can be via Bluetooth or a cable.

<!--T:195-->
==== Device config ====
Device Config contains tools for configuring devices like sensors, receivers, the gas suite, servos and video transmitters.

<!--T:196-->
=== Model select ===
The '''Model Select''' option is accessed by selecting ‘Model select’ from the Model menu. It is used to Select the Current Model, Add a New Model, or Clone or Delete it.

<!--T:197-->
==== Managing model folders ====
ETHOS now allows you to create your own Model Folders to categorize and group your models. Typical Model Folder names may be Airplane, Glider, Heli, Quad, Warbird, Boat, Car, Template, Archive etc.

<!--T:198-->
Until you have created and organized your folders, Ethos will automatically create the '''[Uncategorized]''' folder. This happens when you upgrade to ETHOS version 1.1.0 alpha 17 or later, or when you copy a model from the net or a friend into the \Models folder on the MicroSD card. ETHOS will automatically delete the ‘Uncategorized’ folder when no longer needed.

<!--T:199-->
To create the first folder, tap '''[+]''' to the right of the '''[Uncategorized]''' label. Enter a name in the '''[Create Folder]''' dialog box and click '''[OK]'''. Folder names can have a maximum of 15 characters. Repeat the procedure for other categories. Note that these folders will appear as subfolders in the \Models folder on the SD card.

<!--T:200-->
The model category folders are sorted alphabetically, but the '''[Uncategorized]''' folder always appears last in the list.

<!--T:201-->
Tap the folder name to display a dialog box that allows you to rename or delete the folder. If there were models in the folder being deleted, Ethos will automatically place them in the '''[Uncategorized]''' folder.

<!--T:203-->
===== Moving models to another folder =====
To move the model to another folder, click the model icon and select '''[Change Folder]''' in the dialogue box. Tap the folder you want to move it to.

<!--T:204-->
===== Adding a new model =====
To create a new model, select the model category under which you want to create the model, and then click the '''[+]''' icon to start the model creation wizard. (You may need to create a Model Category first, see above.)

<!--T:205-->
Select the type of model you want to create and follow the instructions.

<!--T:206-->
There are wizards for:

<!--T:207-->
* Airplane
* Glider
* Helicopter
* Multirotor
* Other

<!--T:208-->
The wizards will help you with the basic settings for your model type. Note that model names can have a maximum of 15 characters.

<!--T:209-->
Please note that the elevator setting can be achieved by creating a new aircraft model with 2 ailerons and no tail surfaces and the elevator mixing will be created automatically. The default mix rates are 50%, giving a total of 100% if ailerons and elevator are used at the same time.

<!--T:210-->
The created model will appear in the user-defined model category folder that was active when you started the wizard, and will be sorted alphabetically within each group.

<!--T:211-->
For example, the Airplane wizard will help you with the basic setup of a fixed-wing model. It guides you through a series of steps to configure the basic model setup and allows you to select the number of engines/motors, ailerons, flaps, tail type (e.g. traditional with elevator and rudder or V-tail). Finally, it prompts you to name the model and optionally attach a picture of it. (For a worked example, see the '''Basic Fixed Wing Airplane''' section in the '''Programming Tutorials''' section).

<!--T:212-->
===== Selecting a model =====
Tap on ‘Model select’ to bring up a list of your models.

<!--T:213-->
===== Quick select =====
Long touch or long hold the '''[ENTER]''' key on the model icon to instantly switch to that model.

<!--T:214-->
===== Model management menu =====
Tap on a model to highlight it, then tap on it again to bring up the model management menu.

<!--T:215-->
Options in the model management menu:

<!--T:216-->
* Tap '''Set current model''' to set the highlighted model as the current model.
* You can clone the model to duplicate the model. Note that when you clone a model, ETHOS assigns a new receiver number to the clone. If you give it the old receiver number, it will work, no need to rebind it.
* Change the model folder.
* Alternatively, you can delete the model. Note that the Delete option only appears if the selected model is not the current model.

<!--T:217-->
=== Edit model ===
The '''Edit model''' option is used to edit the basic parameters for the model as set up by the wizard.

<!--T:218-->
==== Name, picture ====
The model can be renamed, or an image can be assigned or changed. When searching for an image, a thumbnail preview will be displayed to help you find the correct image.

<!--T:219-->
==== Model type ====
Changing the model type will cause all mixes to reset.

<!--T:220-->
==== Channel assignments ====
Changing the tailplane or swashplate type will cause all mixes to reset. For other channels, the number of assigned channels can be changed or unassigned.

<!--T:221-->
==== Function switches ====
The six Function Switches are available wherever the '''Active Condition''' parameters are found.

<!--T:222-->
===== Configuration =====
They may be configured as follows:

<!--T:962-->
* 6-Pos with OFF

<!--T:223-->
Pressing any function switch will latch that switch ON. However, pressing a switch that is already ON a second time will turn it OFF, leaving all six function switches OFF.

<!--T:963-->
* 6-POS

<!--T:224-->
Pressing any function switch will latch that switch ON until a different function switch is pressed to latch the newly pressed switch ON.

<!--T:964-->
* 2 x 3-Pos

<!--T:225-->
Breaks the 6 function switches into two groups of 3. Each group can have one switch ON.

<!--T:965-->
* 6 x 2-Pos

<!--T:226-->
Breaks the 6 function switches into 6 latching switches. Each switch can be ON or OFF.

<!--T:966-->
* Momentary

<!--T:227-->
Breaks the 6 function switches into 6 momentary switches. Each switch is ON while depressed.

<!--T:967-->
* Persistent

<!--T:228-->
If enabled, this will cause the function switch to be in the same state when the radio is turned on or the model is reloaded.]

<!--T:992-->
==== Analogs filter ====
A model specific Analog to Digital Converter filter can be turned ON/OFF with this setting. This may improve jitter around stick centre. The default value is OFF in which case the global setting will be used.

<!--T:230-->
Note that there is a global setting on the '''Hardware''' page under '''Analogs Filter'''. This model specific setting will override the global setting.

<!--T:231-->
==== LUA sources ====
Lua Sources must be enabled if your model uses sources created in Lua. This will make them available as sources in the programming.

<!--T:232-->
==== Reset all mixes ====
Enabling '''Reset All Mixes''' will reset all the mixers.

<!--T:233-->
=== Flight modes ===
Flight modes bring incredible flexibility to a model setup, because they allow models to be set up for switch selectable specific tasks or flight behavior. For example, gliders may be set up to have switch selectable modes such as Launch, Cruise, Speed and Thermal. Power planes may have flight modes for Normal precision flying, Take OFF, and Landing with either half or full flaps deployed. Helicopters have modes such as Normal for spool up and take OFF/landing, Idle Up 1 for aerobatic flying, and Idle Up 2 for perhaps 3D.

<!--T:234-->
Flight modes remove much of the switching and trimming burden from the pilot.

<!--T:235-->
The great power of flight modes is that they support independent trims and mixer Variables, and can also be used to enable Mixer lines. Together, these features allow for great flexibility. Please refer to the Introduction to Flight Modes in the Tutorials section to see examples of these features applied.

<!--T:236-->
There are no default flight modes defined. Tap on the default flight mode, and select Edit if you wish to rename it, otherwise select Add to define a new flight mode. There may be up to 20 flight modes.

<!--T:237-->
==== Name ====
Allows the flight mode to be named.

<!--T:968-->
==== Active condition ====
When adding a flight mode the default active condition is inactive, i.e ‘---’. Flight modes may be controlled by switch or button positions, function switches, logic switches, a system event such as throttle cut or hold, or trim positions.

<!--T:969-->
Note that the default flight mode does not have an active condition parameter, because this is the flight mode that is always active when no other flight mode is active. The first flight mode that has its switch ON is the active one. Note that only one flight mode is active at a time.

<!--T:240-->
The active Flight Mode is shown in bold.

<!--T:241-->
==== Fade in/out ====
The times assigned for smooth transitions between flight modes. The example shows one second assigned to each.

<!--T:242-->
==== Trims ====
Displays the trim values.

<!--T:243-->
Trims can operate in two ways with respect to flight modes.

<!--T:244-->
* '''Independent per flight mode:''' With this option, the trim affects the active flight mode only. This option is normally used for the elevator trim, since the elevator trim required will typically vary for each flight mode due for example to differences in wing camber. In fact, this is often the main reason for implementing flight modes.

<!--T:245-->
* '''Shared across flight modes.:''' With this option, the trim value for the stick is shared across all flight modes. This is usually appropriate for aileron trim since this trim usually does not vary across flight modes.

<!--T:246-->
Please refer to the '''Trims''' section for more detail.

<!--T:247-->
Once programed the flight mode selections are displayed in the mixers. Up to 100 flight modes can be programmed. Like most functions in ETHOS the user can program descriptive text Flight Mode names such as Cruise, Speed, Thermal or Normal, Take OFF, Landing.

<!--T:248-->
Please note when adding a new flight mode to a model all mixes using flight modes must be checked for correct operation, because the new flight mode will by default be active in all mixes using flight modes. This is an issue for example when using a Lock mix to lock a specific channel in a specific FM.

<!--T:993-->
==== Flight mode management ====
Tap on a flight mode to bring up a menu which allows you to edit, copy trims, add a new flight mode or delete flight modes.

<!--T:250-->
You can use the 'Move' option to change the priority of a flight mode. The priority of flight modes is in ascending order, and the first one that has its switch ON is the active one.

<!--T:970-->
=== Mixer ===
The '''Mixer''' function forms the heart of the transmitter. This is where the model’s control functions are configured. The Mixer section allows any of the many sources of input to be combined as desired and mapped to any of the output channels. ETHOS has 100 mixer channels available for programming your model. Normally the lowest numbered channels will be assigned to the servos, because the channel numbers map directly to the channels in the receiver. The V20 Internal RF module has up to 24 output channels available.

<!--T:251-->
The upper mixer channels can be used as 'virtual channels' in more advanced programming, or as real channels by using multiple RF modules (Internal + External) and S.Bus. The channel order is a matter of personal preference or convention, or it may be dictated by the receiver.

<!--T:252-->
The source or input to a mix can be chosen from analog inputs such as the sticks, pots and sliders; the toggle switches or buttons; any defined logic switches; the trim switches; any defined channels; a gyro axis; a trainer channel; a timer; a telemetry sensor; a system value such as the main radio voltage or RTC battery voltage; or a ‘special’ value such as 'minimum', 'maximum' or 0.

<!--T:253-->
This section also allows the source to be conditioned by defining weights/rates and offsets, and adding curves (eg Expo). The mix can be made subject to a switch and/or flight modes, and a slow function can be added. (Note that Delays are implemented in the Logic Switches because they are related to switches.) The mixer includes contextual help information that dynamically changes as mixer options are touched. The first line shows the type of mixer used, such as ‘Aileron’, ‘Elevators’, or ‘Free Mix’ etc. Up to 120 mixer lines may be defined.

<!--T:254-->
If your model was created using one of the model creation wizards in the ‘Model select’ function in the System menu, the base mixer lines will be shown when you tap on the ‘Mixer’.

<!--T:255-->
In addition, the most common predefined mixes can be added as well as free mixes that are user configurable.

<!--T:256-->
There is one mix line for each control/mix and a graphic display for that mix. To edit a mixer line, touch the mixer and touch again for the popup menu, then select Edit. Other options are to add a new mix, to switch to the ‘View per Channel’ grouping view (described in a section lower down), to move the mixer line up or down, to clone a mix, or to delete a mix.

<!--T:257-->
Please note that inactive mixer lines are shown greyed out, to assist in debugging.

<!--T:258-->
The radio asks for confirmation before deleting a mix, in case of inadvertent selection.

<!--T:259-->
==== Aileron, elevator, rudder mixer ====
We will use the Ailerons as an example, but the Elevator and Rudder mixes are very similar.

<!--T:260-->
===== Name =====
Ailerons has been filled in as the default name, but it can be changed.

<!--T:261-->
===== Active condition =====
The default active condition is ‘Always On’, which is appropriate for Ailerons. It may be made conditional by choosing from switch or button positions, function switches, flight modes, logic switches, a system event such as throttle cut or hold, or trim positions.

<!--T:262-->
===== Flight modes =====
If any flight modes have been defined, the mix can be made conditional to one or more flight modes. Click on ‘Edit’ and check the boxes for the flight modes in which this mixer line must be active.

<!--T:263-->
===== Curve =====
A standard curve option is Expo, which by default has a value of 0, which means the response is linear (i.e. no curve). A positive value will soften the response around 0, while a negative value will sharpen the response. Any previously defined curve may also be selected. The mixer output will then modified by this curve. Alternatively, a new curve may be added. You can specify more than one curve, each with a condition. If more than one condition is true, the curve higher in the list prevails. Note that the curve is applied before the Rates.

<!--T:264-->
===== Rates =====
Multiple rates can be defined, subject to a switch position, function switch, logic switch, trim position or flight mode. A line is added for each rate. The default rate (i.e. first rates line) is active when none of the other rates are active. There is a small cross inside an arrow on the left of defined rates that can be used to delete a rates line. In the example above three rates have been set up on switch SB.

<!--T:265-->
===== Differential =====
On Ailerons differential (typically more up aileron travel than down) is utilized to reduce adverse yaw and to improve turning/ handling characteristics. A positive value will result in the ailerons having less downward travel, as can be seen in the graph above. (Default = '''0'''. Range '''-100''' to '''+100'''). On Elevator differential may be used for planes wanting less down than up elevator, typically in racing situations. Note that the Differential parameter is only present when you have more than one aileron channel.

<!--T:266-->
===== Channels count =====
Channel count defines how many Output channels are allocated. In this example two ailerons were configured in the model creation wizard.

<!--T:267-->
===== Output1, Output2 =====
The model creation wizard assigned channels 1 and 2 to the ailerons, because the default channel order in the System – Sticks menu was set to '''AETR''', i.e. ailerons, elevator, throttle, rudder. The default can be altered if required, but care must be exercised to assess any other impacts to making a change here. Note that long pressing '''[ENTER]''' on the selected output channel will take you directly to that page in the Outputs.

<!--T:268-->
==== Throttle mixer ====
The Throttle mixer has parameters for managing Throttle Cut and Throttle Hold. Throttle Cut features a throttle input safety interlock, while Throttle Hold has a simple ON/OFFfunction.

<!--T:269-->
===== Input =====
The source for the Throttle mix can be selected here. It defaults to the Throttle stick, but can be changed to an analog, switch, trim, channel, gyro axis, trainer channel, timer or special value.

<!--T:270-->
===== Throttle cut =====
Throttle Cut features a throttle input safety interlock which ensures that the engine or throttle only starts from a low throttle position.

<!--T:971-->
When combined with Low Position Trim (see below), it can be used for managing the throttle and idle settings on glow or gas powered models.

<!--T:271-->
'''Active condition:'''  The active condition may be chosen from switch or button positions, function switches, flight modes, logic switches or trim positions.

<!--T:272-->
'''Sticky:''' When Sticky is in the ON position, the throttle channel output will be switched to the Idle Output Value (default -100%) as soon as Throttle Cut becomes active. When Sticky is in the OFF position, once Throttle Cut becomes active, the throttle channel output will be switched to the Idle Output Value (default -100%) only when the throttle stick goes below the Trigger value (default -85%).

<!--T:273-->
'''Trigger Vvlue:''' The Trigger Value determines the value below which the throttle input triggers the throttle safety interlock. For safety, once the Throttle Cut becomes inactive, the throttle channel output will only leave the Idle Output Value if the throttle input has been below the Trigger Value. This ensures that the engine or motor only starts from a low throttle input value.

<!--T:274-->
===== Throttle hold =====
Throttle Hold provides a simple throttle hold function without the throttle input safety interlock of Throttle Cut above.

<!--T:275-->
'''Active condition:''' The active condition may be chosen from switch or button positions, function switches, flight modes, logic switches or trim positions.

<!--T:276-->
'''Value:''' Once the throttle hold function goes active, the Value setting will be output on the throttle channel. On electric powered models, the throttle hold value is normally (-100%).

<!--T:277-->
===== Flight modes =====
If any flight modes have been defined, the mix can be made conditional to one or more flight modes. Click on ‘Edit’ and check the boxes for the flight modes in which this mixer line must be active.

<!--T:278-->
===== Curve =====
A curve may be defined to modify the throttle channel output. Any previously defined curve may also be selected.

<!--T:279-->
===== Rates =====
Multiple rates can be defined, subject to a switch position, function switch, logic switch, trim position or flight mode. A line is added for each rate. The default rate (i.e. first rates line) is active when none of the other rates are active. There is a small cross inside an arrow on the left of defined rates that can be used to delete a rates line. In the example above three rates have been set up on switch SB.

<!--T:280-->
===== Low position trim =====
For glow and gas engines the '''Low position trim''' is used to adjust the idle speed. The idle speed can vary depending on the weather, etc., so having a way to adjust the idle speed without impacting the full throttle position is important. If 'Low position trim' is enabled, the throttle channel goes to an idle position of -75% when the throttle stick is at the low position (please refer to the channel bar display at the bottom of the screenshot above). The throttle trim lever can then be used to adjust the idle speed between -100% and -50%. Throttle Cut can then be configured to cut the engine with a switch.

<!--T:281-->
==== View per channel option (mixer grouping) ====
With complex mixes it can be difficult to see the effect of other mixer lines on a particular channel. The ‘View per Channel’ option is particularly useful in debugging your mixes, because all the mixes that affect the selected channel are grouped together.

<!--T:283-->
To see the effect of all mixes on the Elevator channel, tap on the Elevators mix, and select ‘View per Channel’ from the popup dialog.

<!--T:284-->
With this ‘View per Channel’ layout the contribution of the various mixes affecting a channel can be easily seen, because the value of each mixer line is shown in both graphical and numerical format.

<!--T:285-->
===== Managing the ‘View per channel’ display =====
'''a) Moving between channels in ‘View per Channel’'''

<!--T:286-->
Clicking on the summary line (highlighted above) will collapse the channel’s sub mixer lines.

<!--T:287-->
'''b) Switching back to table view'''

<!--T:288-->
Clicking on a sub mixer line instead, for example the line highlighted above, will bring up a popup dialog to allow editing the mixer line, switching to Table View, or to delete the mixer line.

==== Predefined mixes ==== <!--T:289-->

===== Airplane library ===== <!--T:290-->

<!--T:292-->
===== Free mix =====
The Mixer function can best be described by making use of a Free Mix, which we will add to the above mixes for illustration purposes. Tap on any Mixer line, and select ‘Add Mix’ from the popup menu to add a new mixer line.

<!--T:972-->
Select Free Mix from the list of available predefined mixes in the Mixer Library.

<!--T:293-->
Next the position for the new mixer line must be chosen.

<!--T:294-->
Tap on ‘Free Mix’ to bring up the edit sub-menu.

<!--T:295-->
Select Edit to open a new screen showing the detailed parameters for the ‘Free Mix’. The graph display on the right will display the mixer output, and the effect of any setting changes that are made.

<!--T:296-->
===== Name =====
A descriptive name can be entered for the Free Mix.

<!--T:297-->
===== Active condition =====
The default active condition is ‘Always On’. It may be made conditional by choosing from switch or button positions, function switches, flight modes, logic switches, a system event such as throttle cut or hold, or trim positions.

<!--T:298-->
===== Flight modes =====
If any flight modes have been defined, the mix can be made conditional to one or more flight modes. Click on ‘Edit’ and check the boxes for the flight modes in which this mixer line must be active.

<!--T:299-->
===== Source =====
The source or input to this mix can be chosen from:

<!--T:300-->
a) analog inputs such as the sticks, pots and sliders

<!--T:301-->
b) the toggle switches or buttons

<!--T:302-->
c) any defined logic switches

<!--T:303-->
d) the trim switches

<!--T:304-->
e) any defined channels

<!--T:305-->
f) gyro axis

<!--T:306-->
g) trainer channel

<!--T:307-->
h) timer

<!--T:308-->
i) telemetry sensor

<!--T:309-->
j) system value (e.g. main radio voltage or RTC battery voltage)

<!--T:310-->
k) "special" value, i.e. minimum, maximum or 0

<!--T:311-->
The mixer line will take the value of the source at any instant as its input.

<!--T:312-->
===== Function type =====
The Function Type defines how the current mixer line interacts with the others on the same channel. There are three function types:  

<!--T:313-->
'''Add'''  

<!--T:314-->
The output of this mixer line will be added to any other mixer lines on the same output channel. Please note that Addition lines can be in any order (A+B+C = C+B+A).  

<!--T:315-->
'''Multiply'''  

<!--T:316-->
The output of this mixer line will be multiplied with the result of other mixer lines above it on the same output channel.  

<!--T:317-->
'''Replace'''  

<!--T:318-->
The output of this mixer line will replace the result of any other mixer lines on the same output channel.  

<!--T:319-->
'''Lock'''

<!--T:320-->
A channel which is "locked" will never be changed by any other mix while the locked mixer line is active. The combination of these operations allows the creation of complex mathematical operations.  

<!--T:321-->
The combination of these operations allows the creation of complex mathematical operations.

<!--T:322-->
===== Curve =====
Curves are applied before the Weight.  

<!--T:323-->
A standard curve option is Expo, which by default has a value of 0, which means the response is linear (i.e. no curve). A positive value will soften the response around 0, while a negative value will sharpen the response.

<!--T:324-->
Any previously defined curve may also be selected. The mixer output will then modified by this curve. Alternatively, a new curve may be added. 

<!--T:325-->
With the Free Mix and some other mixes, you can specify more than one curve, each with a condition. If more than one condition is true, the curve higher in the list prevails.

<!--T:326-->
===== Offset =====
Offset will shift the mixer output up or down by the offset value entered here.

<!--T:327-->
Negative values are allowed.

<!--T:328-->
===== Weight up =====
The mixer output in the positive direction will be scaled by the weight value entered here. Negative values are allowed.

<!--T:329-->
===== Weight down =====
Similarly, the mixer output in the negative direction will be scaled by the weight value entered here.

<!--T:330-->
===== Slow up/down =====
Response of the output can be slowed down with regard to the input change. Slow could for example be used to slow retracts that are actuated by a normal proportional servo.

<!--T:331-->
The value is time in seconds that the output will take to cover the -100 to +100% range.

<!--T:332-->
===== Channels count =====
Channel count defines how many Output channels are allocated.

<!--T:333-->
===== Reverse =====
The output of this mixer line can be reversed or inverted by enabling this option. Please note that servo reversal should be done under Outputs. This option is for getting the logic of the mixing right.

<!--T:334-->
===== Output =====
Any channel can be selected to receive the output from this mixer line. If the Channels Count above is greater than one, then a channel must be configured for each Output.

<!--T:335-->
'''Var'''

<!--T:336-->
The VAR mix assigns a value (or a source) to a channel. Multiple weights may be specified, each associated with a condition such as a flight mode, logic switch or switch position.

<!--T:337-->
'''Trim'''

<!--T:338-->
The Trim mix makes a control behave like a trim. It has separate Up and Down sources, and has the same trim modes as normal trims.

<!--T:339-->
'''Aileron, elevator, rudder'''

<!--T:340-->
Please refer to the detailed Aileron, Elevator, Rudder m i xer description above.

<!--T:341-->
'''Flaps'''

<!--T:342-->
The Flaps mix will mix an Input to one or more channels with individual Weights. It also offers Slow Up and Slow Down options.

<!--T:343-->
'''Throttle'''

<!--T:344-->
The Throttle mix is for motor control and includes Throttle Cut and Throttle Hold options. Please refer to the detailed Throttle mixer discussion above.

<!--T:345-->
'''Aileron to Flap'''

<!--T:346-->
This mix is commonly used on sailplanes so that the flaps move together with the ailerons to increase the model’s aileron response.

<!--T:347-->
'''Aileron to Rudder'''

<!--T:348-->
One of the most commonly used mixes for sailplanes, to help the model have more coordinated turns.

<!--T:349-->
'''Airbrake'''

<!--T:350-->
The Airbrake mix is similar to the Butterfly mix below, except that it is controlled by an ON-OFF active condition.

<!--T:351-->
'''Butterfly'''

<!--T:352-->
Butterfly or crow braking is used to control the rate of descent of an aircraft. The ailerons are set to go up a modest amount, while the flaps go down a large amount. This combination creates a lot of drag, and is very effective for braking and therefore ideal for controlling the landing approach. The input is normally set to a slider (or the throttle stick on a glider). 

<!--T:353-->
Compensation is also needed on the elevator to avoid the glider ballooning up when crow is applied.

<!--T:354-->
'''Camber'''

<!--T:355-->
The Camber mix is functionally the same as the Butterfly mix, but is usually used to apply some camber to the wing surfaces to increase lift.

<!--T:356-->
'''Flap to elevator'''

<!--T:357-->
The Flap to elevator mix is useful for flap/camber/crow compensation, where a custom compensation curve is required.

<!--T:358-->
'''Elevator to camber'''

<!--T:359-->
Also known as Snap Flap, this mix adds camber to the wing as elevator is applied. This allows the wing to generate lift more efficiently when the plane is given pitch commands.

<!--T:360-->
'''Rudder to aileron'''

<!--T:361-->
This mix is used to counter rudder-induced yaw in knife-edge flight.

<!--T:362-->
'''Rudder to elevator'''

<!--T:363-->
This mix can help to improve knife-edge flight when there are coupling issues.

<!--T:364-->
'''Snap roll'''

<!--T:365-->
The snap roll is an auto-rotation maneuver in a stalled condition. During a snap, one wing is stalled while the other is accelerated about the roll axis. This creates a sudden roll-rate acceleration that you cannot obtain by simply inputting aileron. To achieve this condition in a model, several inputs must be given, including elevator, rudder and aileron. For example, you can perform an inside left snap by programming the mix to simultaneously apply up-elevator, left rudder and left aileron for 1 to 2 seconds. Recover from the maneuver by neutralizing the sticks and immediately adding right rudder to correct your loss of heading.

<!--T:366-->
'''Throttle to elevator'''

<!--T:367-->
This mix allows elevator compensation for planes that change pitch on changing throttle.

<!--T:368-->
'''Throttle to rudder'''

<!--T:369-->
This mix will help the plane fly straight when at full throttle; it’s generally needed when flying a vertical up-line.

<!--T:370-->
'''Test mix'''

<!--T:371-->
This mix is great for soak testing servos. It includes a range setting, as well as Slow Up and Slow Down.

<!--T:372-->
'''Offset'''

<!--T:373-->
The Offset mix is used to add a fixed value to the mixer when an offset is required. A common application is for flaps, where the servo horn is offset in one direction in order to maximize the downward flap travel. This results in the flaps being in a half way down position at servo neutral. The Offset mix can then be used to bring the flaps up to the ‘surface neutral’ position when the flaps mixer output is zero.

<!--T:374-->
===== Glider library =====
'''Free mix'''

<!--T:375-->
Please refer to the Free Mix description under the Airplane Library section above.

<!--T:376-->
'''Var'''

<!--T:377-->
The VAR mix assigns a value (or a source) to a channel. Multiple weights may be specified, each associated with a condition such as a flight mode, logic switch or switch position.

<!--T:378-->
'''Trim'''

<!--T:379-->
The Trim mix makes a control behave like a trim. It has separate Up and Down sources, and has the same trim modes as normal trims.

<!--T:380-->
'''Aileron, elevator, rudder'''

<!--T:381-->
Please refer to the detailed Aileron, Elevator, Rudder m i xer description above.

<!--T:382-->
'''Flaps'''

<!--T:383-->
The Flaps mix will mix an Input to one or more channels with individual Weights. It also offers Slow Up and Slow Down options.

<!--T:384-->
'''Throttle'''

<!--T:385-->
The Throttle mix is for motor control and includes Throttle Cut and Throttle Hold options. Please refer to the detailed Throttle mixer discussion above.

<!--T:386-->
'''Aileron to flap'''

<!--T:387-->
This mix is commonly used on sailplanes so that the flaps move together with the ailerons to increase the model’s aileron response.

<!--T:388-->
'''Aileron to rudder'''

<!--T:389-->
One of the most commonly used mixes for sailplanes, to help the model have more coordinated turns.

<!--T:390-->
'''Airbrake'''

<!--T:391-->
The Airbrake mix is similar to the Butterfly mix below, except that it is controlled by an ON-OFF active condition.

<!--T:392-->
'''Butterfly'''

<!--T:393-->
Butterfly or crow braking is used to control the rate of descent of an aircraft. The ailerons are set to go up a modest amount, while the flaps go down a large amount. This combination creates a lot of drag, and is very effective for braking and therefore ideal for controlling the landing approach. The input is normally set to a slider (or the throttle stick on a glider). 

<!--T:394-->
Compensation is also needed on the elevator to avoid the glider "ballooning" up when crow is applied.

<!--T:395-->
'''Camber'''

<!--T:396-->
The Camber mix is functionally the same as the Butterfly mix, but is usually used to apply some camber to the wing surfaces to increase lift.

<!--T:397-->
'''Flap to elevator'''

<!--T:398-->
The Flap to Eelevator mix is useful for flap/camber/crow compensation, where a custom compensation curve is required.

<!--T:973-->
'''Elevator to camber''' 

<!--T:400-->
Also known as Snap Flap, this mix adds camber to the wing as elevator is applied. This allows the wing to generate lift more efficiently when the plane is given pitch commands.

<!--T:401-->
'''Rudder to aileron'''

<!--T:402-->
This mix may be used to counter rudder-induced yaw.

<!--T:403-->
'''Rudder to elevator'''

<!--T:404-->
This mix can help when there are coupling issues. It can also be used for adding a VTail differential function.

<!--T:405-->
'''Throttle to elevator'''

<!--T:406-->
This mix allows elevator compensation for planes that change pitch on changing throttle.

<!--T:407-->
'''Throttle to rudder'''

<!--T:408-->
This mix will help the plane fly straight when at full throttle; it’s generally needed when flying a vertical up-line.

<!--T:409-->
'''Test mix'''

<!--T:410-->
This mix is great for soak testing servos. It includes a range setting, as well as Slow Up and Slow Down.

<!--T:411-->
'''Offset'''

<!--T:412-->
The Offset mix is used to add a fixed value to the mixer when an offset is required. A common application is for flaps, where the servo horn is offset in one direction in order to maximize the downward flap travel. This results in the flaps being in a half way down position at servo neutral. The Offset mix can then be used to bring the flaps up to the ‘surface neutral’ position when the flaps mixer output is zero.

<!--T:413-->
===== Heli library =====
'''Free Mix'''

<!--T:414-->
Please refer to the <u>Free Mix</u> description under the Airplane Library section above.

<!--T:415-->
'''Var'''

<!--T:416-->
The VAR mix assigns a value (or a source) to a channel. Multiple weights may be specified, each associated with a condition such as a flight mode, logic switch or switch position.

<!--T:417-->
'''Trim'''

<!--T:418-->
The Trim mix makes a control behave like a trim. It has separate Up and Down sources, and has the same trim modes as normal trims.

<!--T:419-->
'''Aileron, elevator, rudder'''

<!--T:420-->
Please refer to the detailed Aileron, Elevator, Rudder mix description above.

<!--T:421-->
'''Pitch'''

<!--T:422-->
The Pitch mix mixes the pitch control (default Throttle Stick) to the pitch channel, which is normally channel 6. It controls the collective.

<!--T:423-->
'''Flight mode'''

<!--T:424-->
This mix is used to provide a flight mode control to the FBL controller on the Heli. It may be Normal/Idle Up 1/Idle Up 2 or for example Beginner/Sport/3D.

<!--T:425-->
'''Throttle'''

<!--T:426-->
The Throttle mix is for motor control and includes Throttle Cut and Throttle Hold options. Please refer to the detailed Throttle mixer discussion above.

<!--T:427-->
'''Gyro'''

<!--T:428-->
This mix is used to provide gain settings to the FBL controller, which may for example be flight mode dependent. The gyro channel is often channel 5.

<!--T:429-->
'''Pitch to rudder'''

<!--T:430-->
This is for mixing pitch to the rudder channel.

<!--T:431-->
'''Test mix'''

<!--T:432-->
This mix is great for soak testing servos. It includes a range setting, as well as Slow Up and Slow Down.

<!--T:433-->
'''Offset'''

<!--T:434-->
The Offset mix is used to add a fixed value to the mixer when an offset is required.]

<!--T:435-->
===== Multirotor Library =====
'''Free mix'''

<!--T:436-->
Please refer to the Free Mix description under the Airplane Library section above.

<!--T:437-->
'''Var'''

<!--T:438-->
The VAR mix assigns a value (or a source) to a channel. Multiple weights may be specified, each associated with a condition such as a flight mode, logic switch or switch position

<!--T:439-->
'''Roll, pitch, yaw'''

<!--T:440-->
These mixes are similar to Aileron, Elevator and Rudder mixes. Please refer to the Aileron, Elevator, Rudder mix description above.

<!--T:441-->
'''Flight mode'''

<!--T:442-->
This mix is used to provide a flight mode control to the FBL controller on the Heli. It may be Normal/Idle Up 1/Idle Up 2 or for example Beginner/Sport/3D.

<!--T:443-->
'''Throttle'''

<!--T:444-->
The Throttle mix is for motor control and includes Throttle Cut and Throttle Hold options. Please refer to the detailed   T hrottle mix  discussion above.

<!--T:445-->
'''Test mix'''

<!--T:446-->
This mix is great for soak testing servos. It includes a range setting, as well as Slow Up and Slow Down.

<!--T:447-->
'''Offset'''

<!--T:448-->
The Offset mix is used to add a fixed value to the mixer when an offset is required.]

<!--T:449-->
=== Outputs ===
The Outputs section is the interface between the setup "logic" and the real world with servos, linkages and control surfaces as well as actuators and transducers. In the Mixer we have set up what we want our different controls to do. This section allows these pure logical outputs to be adapted to the mechanical characteristics of the model. This is where we configure minimum and maximum throws, servo or channel reverse, and adjust the servo or channel center point using the PPM center adjustment, or add an offset using subtrim. We can also define a curve to correct any real world response issues. For example, a curve can be used to ensure that left and right flaps track accurately. The various channels are outputs, for example CH1 corresponds to servo plug #1 on your receiver (with the default protocol settings).

<!--T:450-->
The Outputs screen shows two bar graphs for each channel. The lower (green) bar shows the value of the mixer for the channel, while the upper (orange) bar shows the actual value (in both % and μS terms) of the Output after the Outputs processing, which is what is sent to the receiver. In the example above you can see that both the mixer and output values for CH4 Throttle are at 100%.

<!--T:451-->
The channels that are not being output to the RF module are shown with a darker background. In the example above, all eight channels are being transmitted, so they have a lighter grey background.
 '''Note:''' For quick access to this monitor screen, a long press of the enter key from the Mixer screen and Flight Modes screens will jump to the Outputs.

<!--T:452-->
==== Outputs setup ====
Tap on the Output channel to be edited or reviewed.

<!--T:453-->
===== Channel preview =====
A channel preview is shown at the top of the Outputs Setup screen. The mixer value is shown in green, while the channel output value is shown in orange (default theme). A little white marker denotes the 100% point.

<!--T:454-->
===== Name =====
The name can be edited.

<!--T:455-->
===== Invert =====
Will Invert the channel output, typically to reverse servo direction.

<!--T:456-->
===== Min/Max =====
The Channel min and max settings are ‘hard’ limits, i.e. they will never be overridden. They should be set to avoid mechanical binding. Note that they serve as gain or ‘end point’ settings, so reducing these limits will reduce throw rather than induce clipping. 

<!--T:457-->
Note that the limits default to +/- 100.0%, but may be increased here to +/- 150.0%.

<!--T:458-->
 '''Warning:''' When using a redundancy system involving SBUS, servo movements beyond about +/- 125% are not possible. If using more than 125% on the main receiver driving PWM outputs, and this receiver enters failsafe, the servo positions then received from a redundant receiver via SBUS are limited to 125%. In particular, if an output on the main receiver is beyond 125%, then at the point of switching to the redundant receiver, the output will change to 125%.

<!--T:994-->
===== Center/subtrim =====
Used to introduce an offset on the output, typically used to center a servo arm. Note that the endpoints are not affected.

<!--T:463-->
 '''Warning:''' Don't be tempted to use Subtrim to add large offsets - it will build in a large amount of differential into the servo response. The correct way is to add an offset mix.

<!--T:995-->
===== PWM center =====
This is similar to subtrim, with the difference that an adjustment done here will shift the entire servo band of movement (including hard limits). This adjustment won't be visible on the channel monitor because it is effectively done in the servo. The advantage of using PWM Center to mechanically center the control surface is that this separates the centering function from the trimming function.

<!--T:466-->
===== Curve =====
Allows you to select an Expo or custom curve to condition the output. The popup allows to to either select an existing curve, or to add a new curve. After configuring the curve, an Edit button is added so that you can edit the curve easily.

<!--T:467-->
Curves are a quicker and more flexible way of configuring the center and min/max limits of the outputs, and you get a nice graphic. Use a 3-point curve for most outputs, but use a 5-point curve for things such as the second aileron and flap, so you can synchronize the travel at 5 points. When using a curve it is good practice to leave Min, Max and Subtrim at their 'pass thru' values of -100, 100 and 0 respectively (or -150, 150 and 0 if using extended limits).

<!--T:468-->
===== Slow up/down =====
Response of the output can be slowed down with regard to the input change. Slow could for example be used to slow retracts that are actuated by a normal proportional servo. The value is time in seconds that the output will take to cover the -100 to +100% range.

<!--T:469-->
===== Delay =====
Please note that a delay function is available under Logic Switches.

<!--T:996-->
=== Timers ===
There are 3 fully programmable timers that can count either up or down. 

<!--T:471-->
Touching any timer line brings up a popup with options to reset or edit that timer, add a new timer, or to move or copy/paste the timer.

<!--T:975-->
==== Name ====
Allows the timer to be named.

<!--T:473-->
==== Mode ====
The timer can count Up or Down.

<!--T:474-->
==== Alarm/start value ====
If the timer has been set to count Up, the Start Value parameter sets the Alarm Value at which the timer triggers the configured alerts.

<!--T:475-->
If the timer has been set to count Down, the Alarm Value parameter sets the Start Value from which the timer counts down. When it reaches zero, it triggers the configured alerts.

<!--T:997-->
==== Sound ====
This setting determines whether the countdown alert is mute, or a beep or spoken value. When Sound mode = Beep there is a longer beep when the timer is expired.

<!--T:477-->
==== Haptic ====
Enables haptic feedback to signal that the timer has elapsed.

<!--T:478-->
==== Countdown start ====
The timer value from which the countdown alerts start.

<!--T:479-->
==== Countdown step ====
The interval at which countdown alerts are made.

<!--T:480-->
==== Timer elapsed audio file ====
An audio file may be selected to be played when the timer has elapsed.

<!--T:998-->
==== Active condition ====
The active condition parameter which determines when the timer is running has the following options:

<!--T:482-->
===== Always ON =====
Always On counts all the time.

<!--T:483-->
===== Throttle absolute =====
The timer runs whenever the throttle stick isn't at idle.

<!--T:484-->
===== Throttle percentage =====
The timer counts up/down as a percentage of the full stick range.

<!--T:485-->
===== Throttle trigger =====
Throttle Trigger starts the timer the first time throttle is advanced. 

<!--T:486-->
===== Switch positions =====
The timer may also be enabled by a switch position.

<!--T:487-->
===== Logic switch positions =====
The timer may also be enabled by a logic switch.

<!--T:488-->
==== Reset ====
The timer can be reset by switch positions, function switches, logic switches or trim switch positions. Not that the timer will be held in reset while the Reset condition is valid.

<!--T:489-->
==== Persistent ====
Turning Persistent to On allows storing the timer value in memory when the radio is powered OFF or the model is changed, and will be reloaded next time the model is used.

<!--T:999-->
=== Trims ===
The Trims section allows you to configure the Trim Range and Trim Step size, or to configure Independent Trims for each of the 4 control sticks. It also allows Cross Trims to be configured.

<!--T:491-->
There are four sets of Trims settings, one set for each stick. For example, you can have independent elevator trims per flight mode, while leaving the aileron and rudder trims as common or combined.

<!--T:492-->
==== Trim range ====
The default trim range is +/- 25%. The range may be changed to cover up to the full stick range of 100%. Care must be taken with this option, as holding the trim tabs for too long might add so much trim as to make your model unflyable.

<!--T:493-->
==== Trim step ====
The Trim Step parameter allows trims to be disabled, or to configure the granularity of the trim switch steps, from Extra Fine through Medium to Coarse, or Exponential. The Exponential setting gives fine steps near the center, and coarse steps further out. Custom allows the trim step to be specified as a percentage.

<!--T:494-->
==== Independent trim per flight mode ====
If you are using Flight Modes, then this setting enables the relevant trim to be independent for each flight mode, instead of being common to all flight modes.

<!--T:495-->
==== Cross trim ====
Cross trims can be set up for each trim stick, so you can nominate which trim switch to use for each stick.

<!--T:496-->
=== RF system ===
This section is used to configure the Owner Registration ID, and the internal and/or external RF modules.

<!--T:497-->
==== Owner registration ID ====
The Owner Registration ID is an 8 character ID that contains a unique random code, which can be changed if desired. This ID becomes the Owner Registration ID when registering a receiver (see below). Enter the same code in the Owner ID field of your other transmitters you want to use the Smart Share feature with them. This must be done before creating the model you want to use it on.

==== Internal module ==== <!--T:498-->

<!--T:499-->
===== Overview =====
The X20 TD-ISRM internal RF module is a new design that provides tandem 2.4GHz and 900MHz RF paths. It can operate in 3 modes, i.e. ACCESS, ACCST D16 (see below) or TD MODE (see further below).

<!--T:500-->
'''ACCESS mode'''

<!--T:501-->
In ACCESS mode the 2.4G and 900M RF paths work in tandem with one set of ACCESS controls. There can be three 2.4G receivers registered and bound or three 900M receivers registered and bound or a combination of 2.4G and 900M for a total of three receivers. In ACCESS mode with a combination of 2.4G and 900M receivers the telemetry for the 2.4G and 900M RF links are active at the same time. The sensors are identified in telemetry as 2.4G or 900M. Please note that the 2.4G band supports 24 channels, while the 900M band supports 16 channels.

<!--T:502-->
There is a new ETHOS telemetry receiver source feature named RX. RX provides the receiver number of the active receiver sending telemetry. RX is available in telemetry like any other sensor for real time display, Logic Switches, Special Functions and data logging.

<!--T:503-->
'''ACCST D16 mode'''

<!--T:504-->
In ACCST D16 the TD-ISRM becomes a single 2.4G RF path.

<!--T:505-->
'''TD mode'''

<!--T:506-->
In TD Mode the TD-ISRM is in a low latency long range mode using the 2.4G and 900M RF links in Tandem to work with the new Tandem receivers. Tandem supports 24 channels on both bands.

<!--T:507-->
===== State =====
The Internal Module can be On or Off.

<!--T:508-->
===== Type =====
Transmission mode of the internal RF module. The X20/X20S models operate on the 2.4GHz and/or the 900MHz band. The ACCESS and TD (Tandem) modes can operate on both the 2.4GHz and/or the 900MHz band simultaneously (or individually), while the ACCST D16 operates only on the 2.4GHz band. The Mode must match the type supported by the receiver or the model will not bind! After a Mode change, carefully check model operation (especially Fail-safe!) and fully verify that all receiver channels are functioning as intended.

<!--T:509-->
===== Type: ACCESS =====
ACCESS changes the way receivers are bound and connected with the transmitter. The process is broken into two phases. The first phase is registering the receiver to the radio or radios it is to be used with. Registration only needs to be performed once between each receiver / transmitter pair. Once registered, a receiver can be bound and re-bound wirelessly with any of the radios it is registered with, without using the bind button on the receiver.

<!--T:510-->
<s>[Having selected the ACCESS mode, the following parameters must be set up:]</s>

<!--T:511-->
'''State'''

<!--T:512-->
Enable or disable the 2.4G RF module.

<!--T:513-->
'''2.4G Antenna'''

<!--T:514-->
Select Internal or External (on ANT1 connector) Antenna. Although the RF stage has built-in protection, it is good practice to ensure that an external antenna has been fitted before selecting the External antenna. Please note that the antenna selection is on a per model basis, so each time a model change selection is made ETHOS sets the antenna mode for the given model.

<!--T:515-->
'''Phase One: Registration'''

<!--T:516-->
a) Initiate the registration process by selecting [Register]. A message box with "Waiting...." will pop up with a repeating "Register" voice alert.

<!--T:517-->
b) While holding down the bind button, power up the receiver, and wait for the red & green LEDs to become active. The "Waiting..." message changes to "Receiver Connected", and Rx Name field will be  filled in automatically.

<!--T:518-->
c)  At this stage the Reg. ID and UID can be set:

<!--T:519-->
• '''Reg. ID:''' The Registration ID is at owner or transmitter level. This should be a unique code for your X20/X20S and transmitters to be used with Smart Share. It defaults to the value in the Owner Registration ID setting described above at the start of this section, but can be edited here. If two radios have the same ID you can move receivers (with the same Receiver No for a given model) between them by simply using the power on bind process.

<!--T:520-->
• '''RX name:''' Filled in automatically, but the name can be changed if desired. This can be useful if you are using more than one receiver and need to remember for example that RX4R1 is for Ch1-8 or RX4R2 is for Ch9-16 or RX4R3 is for Ch17-24 when rebinding later. A name for the receiver can be entered here.

<!--T:521-->
• '''UID''' is used to distinguish between multiple receivers used simultaneously in a single model. It can be left at the default of 0 for a single receiver. When more than one receiver is to be used in the same model, the UID should be changed, normally 0 for Ch1-8, 1 for Ch9-16, and 2 for Ch17-24. Please note that this UID cannot be read back from the receiver, so it is a good idea to label the receiver.

<!--T:522-->
d) Press '''[Register]''' to complete. A dialog box pops up with "Registration ok". Press '''[OK]''' to continue.

<!--T:523-->
e) Turn the receiver off. At this point the receiver is registered, but it still needs to be bound to the transmitter to be used. It is now ready for binding.

<!--T:524-->
'''Phase Two: Model ID, Channel Range, Binding, and Module Options'''

<!--T:525-->
'''Model ID'''

<!--T:526-->
When you create a new model, the Model ID is automatically allocated. The Model ID must be a unique number because the Smart Match function ensures that only the correct Model ID will be bound to. This number is sent to the receiver during binding, so that it will then only respond to the number it was bound to. Receiver matching is still as important as it was before ACCESS. The Model ID can be changed manually. Note also that the Model ID is changed when the model is cloned.

<!--T:527-->
'''Channel range'''

<!--T:528-->
Since ACCESS supports 24 channels, you normally choose Ch1-8, Ch1-16, Ch9-16 or Ch17-24 for the receiver being set up. Note that Ch1-16 is the default.

<!--T:529-->
The choice of transmitter channel range also affects the transmitted update rates. Eight channels are transmitted every 7ms. If using more than 8 channels, then the channel update rates are as follows:
{| class="wikitable"
|Channel Range
|Update Rate
|Notes
|-
|1-24
|21ms
|Ch1-8, then Ch9-16, then Ch17-24 sent in rotation
|-
|1-16
|14ms
|Ch1-8, Ch9-16, sent alternately
|-
|1-8
|7ms 
|Ch1-8
|-
|Racemode
|4ms
|Digital servos only
|}
'''Racing mode'''

<!--T:530-->
Racing mode offers a very low latency of 4ms with RS receivers. The TD-ISRM module and the RS receiver must be on v2.1.7 or later.

<!--T:531-->
If the Channel Range is set to Ch1-8, it becomes possible to select a source (e.g a switch) which will enable Race Mode. Once the RS receiver has been bound (see below), and Racing mode has been enabled, the RS receiver must be re-powered for Racing mode to take effect.

<!--T:532-->
'''Bind'''

<!--T:533-->
Receiver binding enables a registered receiver to be bound to one of the transmitters it has been registered with in phase 1, and will then respond to that transmitter until re-bound to another transmitter. Be certain to perform a range check before flying themodel.

<!--T:534-->
 '''Warning – very important:''' Do not perform the binding operation with an electric motor connected or an internal combustion engine running.

<!--T:536-->
# Turn the receiver power off.
# Confirm that you are in ACCESS mode.
# Receiver 1 [Bind]: Initiate the binding process by selecting [Bind]. A voice alert will announce "Bind" every few seconds to confirm that you are in bind mode. A popup will display "Waiting for receiver….".
# Power up the receiver without touching the bind button. A message box will pop up 'Select device' and the name of the receiver you have just powered on.
# Scroll to the receiver name and select it. A message box will pop up indicating that binding was successful.
# Turn OFF both the transmitter and the receiver.
#  Turn the transmitter on and then the receiver. If the Green LED on the receiver is on, and the Red LED is off, the receiver is linked to the transmitter. The receiver/transmitter module binding will not have to be repeated, unless one of the two is replaced.

<!--T:537-->
The receiver will only be controlled (without being affected by other transmitters) by the transmitter it is bound to. 

<!--T:538-->
The receiver selected will now show for RX1 the name next to it.

<!--T:539-->
The receiver is now ready for use.

<!--T:540-->
Repeat for Receiver 2 and 3 if applicable.

<!--T:541-->
Refer also to the Telemetry section for a discussion on RSSI.

<!--T:542-->
'''Adding a redundant receiver'''

<!--T:543-->
A second receiver may be bound to an unused slot, e.g. either RX2 or RX3 to provide redundancy in case of reception problems. Either a 2.4G or 900M receiver may be the backup for redundancy. Our example below shows a 900M receiver being added.

<!--T:544-->
# Connect the SBUS Out port of the redundant receiver to the SBUS IN port of the main receiver.
# Power up the receivers (the redundant receiver can be powered via the SBUS cable.
# Register the new receiver.
# Switch OFF the receivers.
# Tap 'Bind' on either the RX2 or RX3 line.
# Power up the receivers. Select the R9 redundant receiver. Tap on OK. Ensure that the Green LED on the redundant receiver is ON. The redundant receiver is now bound.
# The redundant receiver will now be listed.
 '''Note:''' Although it is possible to bind both the main and redundant receivers to the same UID by powering them up individually, you will not have access to the Rx options while both are powered up.
'''Set - receiver options'''

<!--T:545-->
Tap the Set button next to Receiver 1, 2 or 3, and to bring up Receiver Options:

<!--T:546-->
'''Options'''

<!--T:547-->
Telemetry 25mW: Checkbox to limit telemetry power to 25mW (normally 100mW), possibly required if for example servos experience interference from RF being sent close to them.

<!--T:548-->
High PWM speed: Servo update rates are completely determined by the receiver. This checkbox enables a 7ms PWM update rate (vs 18ms standard). Ensure that your servos can handle this update rate.

<!--T:549-->
Please refer to the Channel Range (Access) section for details on the update rate set at the transmitter.

<!--T:550-->
Port: Allows selection of the SmartPort on the receiver to use either S.Port, F.Port 
or the FBUS (F.Port2) protocol. The F.Port protocol was developed with the Betaflight team to integrate the separate SBUS and S.Port signals. FBUS (F.Port2) also enables one Host device to communicate with several Slave devices on the same line. For more information about the port protocol, please refer to the protocol explanation on the official FrSky website.

<!--T:551-->
SBUS:  Allows selection of SBUS-16 channel or SBUS-24 channel mode. Be aware that all connected SBUS devices have to support the SBUS-24 mode in order to activate the new protocol. SBUS-24 is an FrSky development of the SBUS-16 Futaba protocol.

<!--T:552-->
Channel mapping: The receiver Options dialog also gives the ability to Remap channels to the receiver pins.

<!--T:553-->
'''Share'''

<!--T:554-->
The Share feature provides the ability to move the receiver to another ACCESS radio having a different Owner Registration ID. When the Share option is tapped, the receiver green LED turns off.

<!--T:555-->
On target radio B, navigate to the RF System section and Receiver(n) and select Bind. Note that the Share process skips the Registration step on Radio B, because the Owner Registration ID is transferred from radio A. The receiver name from the source radio pops up. Select the name, the receiver will bind and its LED will go green.

<!--T:556-->
A "Bind successful" message will pop up.

<!--T:557-->
Tap on OK. Radio B now controls the receiver. The receiver will remain bound to this radio until you choose to change it.

<!--T:558-->
Press the EXIT button on Radio A to stop the Share process.

<!--T:559-->
The receiver can be moved back to radio A by rebinding it to radio A.
 '''Note:''' You do not need to use 'Share' if all your radios are using the same Owner ID / registration number. You can simply put the radio you want to use in bind mode, turn on the receiver, select the receiver in the radio and it will bind with that radio. You can switch to another radio the same way. It is best to keep the model receiver numbers the same when copying the models.

<!--T:1000-->
'''Reset bind'''

<!--T:560-->
If you change your mind about sharing a model, select 'Reset bind' to clean up and restore your bind. Power cycle the receiver, and it will be bound to your transmitter.

<!--T:561-->
'''Reset – Receiver'''

<!--T:562-->
Tap on the Reset button to Reset the receiver back to factory settings and clear the UID. The receiver is unregistered with X20.

<!--T:1001-->
===== Type: ACCST D16 =====
Mode ACCST D16 is for the ACCST 16ch two-way full duplex transmission, also known as the "X"-mode. For use with the legacy “X” series receivers.

<!--T:574-->
'''2.4G'''

<!--T:575-->
ACCST D16 operates on 2.4G, so the 2.4G RF section is on by default.

<!--T:576-->
'''Antenna'''

<!--T:577-->
Select Internal or External (on ANT1 connector) Antenna. Although the RF stage has built-in protection, it is good practice to ensure that an external antenna has been fitted before selecting the External antenna. Please note that the antenna selection is on a per model basis, so each time a model change selection is made ETHOS sets the antenna mode for the given model.

<!--T:578-->
'''Model ID'''

<!--T:579-->
When you create a new model, the Model ID is automatically allocated. The Model ID must be a unique number because the Model Match function ensures that only the correct Model ID will be bound to. This number is sent to the receiver during binding, so that it will then only respond to the number it was bound to. The Model ID can be changed manually.

<!--T:580-->
'''Channel range'''

<!--T:581-->
Choice of which of the radio's internal channels are actually transmitted over the air. In D16 mode you can choose between 8 channels with data sent every 9ms, and 16 channels with data sent every 18ms.

<!--T:582-->
Please note that servo update rates are completely determined by the receiver. For ACCST please refer to your receiver manual for details on selecting the 9ms HS (High PWM Speed) mode. Ensure that your servos can handle this update rate.

<!--T:583-->
'''Bind'''

<!--T:584-->
# Initiate the binding process by selecting [Bind]. A voice alert will announce ‘Bind’ every few seconds to confirm that you are in bind mode. In D16 mode a pop-up menu will open during bind to allow selection of the operation mode of the receiver. The options refer to the PWM outputs, and apply to receivers that support choosing between these 4 options using jumpers. Ensure that the receiver and RF module firmware support this option. If they do not, it is necessary to do a regular bind with the bind button (please refer to the receiver manual). There are 4 modes with the combinations of Telemetry ON/OFF and channel 1-8 or 9-16. This is useful when using two receivers for redundancy or to connect more than 8 servos using two receivers.
# Power up the receiver, putting it into bind mode as per the receiver instructions. (Generally done by holding down the Failsafe button on the receiver during power up.)
# The Red and Green LEDs will come on. The Green LED will go off, and the Red LED will flash when the binding process is completed.
# Tap OK on the transmitter to end the Bind process, and power cycle the receiver.
#  If the Green LED on the receiver is on, and the Red LED is off, the receiver is linked to the transmitter. The receiver/transmitter module binding will not have to be repeated, unless one of the two is replaced. The receiver will only be controlled (without being affected by other transmitters) by the transmitter it is bound to.
 '''Warning:''' Do not perform the binding operation with an electric motor connected or an internal combustion engine running.

<!--T:588-->
===== Type: TD MODE =====
ACCESS and TD MODE change the way receivers are bound and connected with the transmitter. The process is broken into two phases. The first phase is registering the receiver to the radio or radios it is to be used with. Registration only needs to be performed once between each receiver / transmitter pair. Once registered, a receiver canbe bound and re-bound wirelessly with any of the radios it is registered with, without using the bind button on the receiver.

<!--T:589-->
'''2.4G'''

<!--T:590-->
The 2.4G RF module is already enabled. Select Internal or External (on ANT1 connector) Antenna. Although the RF stage has built-in protection, it is good practice to ensure that an external antenna has been fitted before selecting the External antenna. Please note that the antenna selection is on a per model basis, so each time a model change selection is made ETHOS sets the antenna mode for the given model.

<!--T:591-->
'''Antenna'''

<!--T:592-->
Select Internal or External (on ANT2 connector) Antenna. Although the RF stage has built-in protection, it is good practice to ensure that an external antenna has been fitted before selecting the External antenna. Please note that the antenna selection is on a per model basis, so each time a model change selection is made ETHOS sets the antenna mode for the given model.

<!--T:593-->
'''Model ID'''

<!--T:594-->
When you create a new model, the Model ID is automatically allocated. The Model ID must be a unique number because the Smart Match function ensures that only the correct Model ID will be bound to. This number is sent to the receiver during binding, so that it will then only respond to the number it was bound to. Receiver matching is still as important as it was before ACCESS.

<!--T:595-->
'''Channel range'''

<!--T:596-->
Choice of which of the radio's internal channels are actually transmitted over the air. In D16 mode you can choose between 8 channels with data sent every 9ms, and 16 channels with data sent every 18ms

<!--T:597-->
'''Bind'''

<!--T:599-->
'''Phase one: Registration'''

<!--T:600-->
a) Initiate the registration process by selecting [Register]. A message box with 'Waiting....' will pop up with a repeating ‘Register’ voice alert.

<!--T:601-->
b)  While holding down the bind button, power up the receiver, and wait for the red & green LEDs to become active. The 'Waiting...' message changes to ‘Receiver Connected’, and Rx Name field will be filled in automatically.

<!--T:602-->
c) At this stage the Reg. ID and UID can be set:

<!--T:603-->
• Reg. ID: The Registration ID is at owner or transmitter level. This should be a unique code for your X20/X20S and transmitters to be used with Smart Share. It defaults to the value in the Owner Registration ID setting described above at the start of this section, but can be edited here. If two radios have the same ID you can move receivers (with the same Receiver No for a given model) between them by simply using the power on bind process.

<!--T:604-->
•  RX name: Filled in automatically, but the name can be changed if desired. This can be useful if you are using more than one receiver and need to remember which is bound to which channels.

<!--T:605-->
• The UID is used to distinguish between multiple receivers used simultaneously in a single model. It can be left at the default of 0 for a single receiver. When more than one receiver is to be used in the same model, the UID should be changed. Please note that this UID cannot be read back from the receiver, so it is a good idea to label the receiver.

<!--T:606-->
d) Press [Register] to complete. A dialog box pops up with 'Registration ok'. Press [OK] to continue.

<!--T:607-->
e) Turn the receiver off. At this point the receiver is registered, but it still needs to be bound to the transmitter to be used. It is now ready for binding.

<!--T:608-->
'''Phase two: – Model ID, Channel Range, Binding, and Module Option'''

<!--T:609-->
 '''Caution:''' Do not perform the binding operation with an electric motor connected or an internal combustion engine running.

<!--T:1002-->
=== Fail-safe emergency rates ===
When Fail-safe is enabled, 3 modes are available: No signal, Hold, Custom.

<!--T:977-->
* '''No signal''': when signal is lost, the receiver does not send a control signal to the rates on any channel. To use this type, select it from the menu and wait 9 seconds for the Fail-safe setting change to take effect.
* '''Hold''': the receiver maintains the rates as they were before the signal was lost. To use this type, select it from the menu and wait 9 seconds for the Fail-safe setting change to take effect.
* '''Custom''': the receiver keeps the rate value on all channels as you preselect it. Select the Fail-safe setting menu. Switch from Disconnect/Hold/Not Set to „Custom“. Select the channel for which you want to set fail-safe rates and confirm the selection. Then set the rates on each desired channel and confirm the selection. Wait 9 seconds for the Fail-safe setting change to take effect.

 <!--T:978-->
'''Note:''' If the fail-safe rates are disabled on the transmitter, the fail-safe rates set on the receiver will automatically be used. The S.BUS connector does not support „Disconnect“ mode, and will always use „Hold“ or „Custom“ mode.''

<!--T:1003-->
=== Range check ===
A pre-flight range check should be performed before each flight. Select the „RF System“ section, select either the internal or external module, select „Action“, then „Range Check“ and confirm the selection. In range check mode, the effective range of the transmitter is reduced to 1/30. Press „Range Check“ again to return to normal mode.

<!--T:613-->
A „Range Check“ voice alert will sound every few seconds to confirm that you are in range check mode. A pop-up window on the display will show the receiver UID and the VFR% and RSSI values to evaluate the reception quality. Under ideal conditions, when the transmitter and receiver are both 1 m above the ground, the Alarm should appear at a distance of approximately 30 m from each other.

<!--T:979-->
=== Telemetry ===
FrSky offers a very comprehensive telemetry system. The power of telemetry has lifted the RC hobby to a whole new level, and allows much more sophistication and a much richer modeling experience.

<!--T:614-->
==== Smart port – telemetry ====
FrSky's series of sensors are a hub-less design. Smart Port (S.Port) uses a three wire physical bus comprising of Gnd, V+ and Signal. S.Port telemetry devices are daisy chained together in any sequence and plugged into the S.Port connection on compatible X and S and later series receivers. The receiver can achieve half duplex communication at a rate of 57600bps (F.Port and FBUS are faster) with many compatible devices through this connection with little or no manual set up.

<!--T:615-->
==== Physical ID ====
Smart Port supports up to 28 nodes including the host receiver. Each node must have a unique Physical ID to ensure that there are no clashes in communication. Physical IDs may range between 00 hex and 1B hex (between 00 and 27 decimal).
{| class="wikitable"
|Dec
|Hex
|Default Physical ID
|-
|00
|00
|Vario
|-
|01
|01
|FLVSS
|-
|02
|02 
|Current
|-
|03
|03
|GPS
|-
|04
|04
|RPM
|-
|05
|05
|SP2UART (Host)
|-
|06
|06
|SP2UART (Remote)
|-
|07
|07
|FAS-xxx
|-
|08
|08
|TBD(SBEC)
|-
|09
|09
|Air Speed
|-
|10
|0A
|ESC
|-
|11
|0B
|
|-
|12
|0C
|XACT Servo
|-
|13
|0D
|
|-
|14
|0E
|
|-
|15
|0F
|
|-
|16
|10
|SD1
|-
|17
|11
|
|-
|18
|12
|VS600
|-
|19
|13
|
|-
|20
|14
|
|-
|21
|15
|
|-
|22
|16
|Gas Suite
|-
|23
|17
|FSD
|-
|24
|18
|Gateway
|-
|25
|19
|Redundancy Bus
|-
|26
|1A
|SxR
|-
|27
|1B
|Bus Master
|}
The table above lists the default Physical IDs of FrSky S.Port devices. Please note that if you have more than one of any of them, the Physical ID of the duplicate devices must be changed to ensure that each device in the S.Port chain has a unique Physical ID.

<!--T:616-->
==== Application ID ====
Each sensor may have multiple Application IDs, one for each sensor value being sent. 

<!--T:617-->
The Physical ID and the Application ID are independent and unrelated. For example the Variometer sensor has just one Physical ID (default 00), but two Application IDs: one for Altitude (0100) and the other for Vertical Speed (0110).

<!--T:618-->
Another example is the FLVSS Lipo Voltage sensor, which has a Physical ID (default 01), and an Application ID for Voltage (0300). If you want to use two FLVSS sensors to monitor two 6S Lipo packs, you will need to use Device Config to change the Physical ID 
of the second FLVSS to an empty slot (say 0F hex), and also to change the Application ID from say 0300 to 0301. Because the Physical ID and the Application ID are independent and unrelated, both must be changed. The Physical ID must be changed for exclusive 
communication with the host receiver, and the Application ID must be changed so the receiver can distinguish between the data from Lipo 1 and 2.
{| class="wikitable"
|Device
|Application ID (hex)
|Notes
|-
|Vario
|010x
011x
|Altitude
Vertical Speed
|-
|FLVSS Lipo Voltage Sensor
|030x
|Lipo Voltage
|-
|FAS100S Current Sensor
|020x
021x
040x
041x 
|Current
VFAS
Temperature 1
Temperature 2
|-
|Xact Servo
|068x
|Current, Voltage, Temp, Status
|}
Above are a few example Application IDs. Please note that the Application ID parameter in Device Config presents a drop-down list of 4 digits to choose from; the default 4th digit is 0, but may be changed in a range of 0 to F hex (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F) to ensure that all Application IDs are unique.

<!--T:619-->
Please also note that:

<!--T:620-->
a)  A device may have more than one range of Application IDs, see for example the Current Sensor above.

<!--T:621-->
b) Where two redundant receivers have their S.Port telemetry ports connected, then packets for a particular sensor received by either receiver will be merged even if the redundant receiver is on a different band or module.

<!--T:622-->
==== S.Port key features: ====
Each value received via telemetry is treated as a separate sensor, that has its own properties such as:

<!--T:623-->
* the sensor value
* the S.Port Physical ID number and Data ID (aka Application ID)
* the name of the sensor (editable)
* the unit of measurement
* the decimal precision
* option to log to the SD card

<!--T:624-->
The sensor also keeps track of its min/max value.

<!--T:625-->
As already mentioned more than one of the same sensor type can be connected, but the Physical ID must be changed in Device Config (or using the FrSky Airlink App or SBUS servo changer SCC) to ensure that each sensor in the S.Port chain has a unique Physical ID. Examples are a sensor for each cell in a 2 x 6S Lipo, or monitoring individual motor currents in a multi-motor model.

<!--T:626-->
The same sensor can be duplicated, for example with different units, or for use in calculations such as absolute altitude, altitude above starting point, distance, etc. 

<!--T:627-->
Each sensor can be individually reset with a special function, so for example you can reset your altitude offset to your starting point without losing all the other min/max values.

<!--T:628-->
With FrSky sensors, once set up, they are auto-discovered whenever the complete system is powered up. However, when initially installed, they must be manually "discovered" in order for the system to recognize them.

<!--T:629-->
Telemetry sensors can be:

<!--T:630-->
* played in voice announcements
* used in logical switches
* used in Inputs for proportional actions
* displayed in custom telemetry screens
* seen directly on the telemetry setup page without having to configure a custom telemetry screen

<!--T:631-->
Displays are updated as data is received, and loss of sensor communication is detected.

<!--T:1004-->
==== FBUS – control and telemetry ====
The FBUS (previously F.Port 2.0) protocol is the upgraded protocol which integrates SBUS for control and S.Port for telemetry into one line. This new protocol enables one Host device to communicate on one line with several Slave accessories. For example FBUS servos are controlled on one daisy-chained connection while also sending their servo telemetry back to the receiver on the same connection. All FBUS devices connected to an ACCESS receiver (Host) can be configured wirelessly from the ACCESS radio on this protocol.

<!--T:633-->
The FBUS baud rate is 460,800 bps, while F.Port was 115,200 and S.Port 57,600 bps. This fact alone makes the three protocols incompatible with each other.

<!--T:634-->
==== Telemetry features in ACCESS ====
Single receiver telemetry with ACCESS works in the same way as before with ACCST.

<!--T:635-->
==== Multi receiver telemetry ====
ACCESS Trio Control provides the ability to have three receivers for each RF path registered and bound in ACCESS transmitters. The three receivers are bound in the transmitter RF screen in positions RX1, RX2 and RX3 that enables the ability to access the receivers individually to map the port pins and make other changes to the RX. 

<!--T:636-->
ACCESS normally has one inbound telemetry path for each RF link or one link for each ISRM RF module. The Tandem systems are an exception with one TD ISRM that has a 2.4 and 900m section for two RF paths. The telemetry source receiver may change during a flight depending on RF conditions. ETHOS has an RX sensor that displays the telemetry source real-time and data logs the RX sensor data. 

<!--T:637-->
The most common application using S.Port would be by daisy chaining the S.Port sensor chain to all 3 receivers, which should be sharing a common power supply. 

<!--T:638-->
* Register and bind the receivers (refer to Model Setup).
* Connect the sensor and receiver Smart Ports in a daisy chain fashion.
* Discover new sensors (refer to Telemetry Setup), and test carefully that Smart Portswitching is working correctly.

<!--T:639-->
The telemetry source will automatically switch depending on the active RX. The RX internal sensor displays the ID of the active RX that is sending telemetry, i.e. RX1, RX2 or RX3.

<!--T:640-->
When the receiver telemetry source changes, linking of the receiver S.Ports will automatically continue telemetry from S.Port connected external sensors. However please note that it does not link internal receiver sensors. RSSI, VFR, RxBatt, ADC2 and RX(n) sensor data is sent for the source receiver, so that does change depending on the source.

<!--T:641-->
Simultaneous telemetry from three receivers will come later. Further developments are expected in this area.

==== Sensor types: ==== <!--T:642-->

<!--T:643-->
===== 1. Internal sensors =====
FrSky radios and receivers have built-in telemetry functions to monitor the strength of the signal being received by the model.

<!--T:1005-->
==== RSSI ====
Receiver Signal Strength Indicator (RSSI): A value transmitted by the receiver in your model to your transmitter that indicates how strong the signal is that is being received by the model. Warnings can be set up to warn you when it drops below a minimum value, indicating that you’re in danger of flying out of range. Factors affecting the signal quality include external interference, excessive distance, badly oriented or damaged antennas etc. 

<!--T:645-->
'''ACCESS'''

<!--T:646-->
The default alarms for ACCESS are 35 for 'RSSI Low' and 32 for 'RSSI Critical'. Loss of control will happen when the RSSI drops to around 28.

<!--T:647-->
'''ACCST'''

<!--T:648-->
The default alarms for ACCESS are 35 for 'RSSI Low' and 32 for 'RSSI Critical', while for ACCST they are 45 and 42 respectively. Loss of control will happen when the RSSI drops to around 28 for ACCESS and 38 for ACCST. 

<!--T:649-->
The warning for when telemetry is lost completely is announced as 'Telemetry Lost'. Be aware that further alarms will NOT sound, because the telemetry link has failed, and the radio can no longer warn you of an RSSI or any other alarm condition. In this situation it is wise to turn back to investigate the problem.

<!--T:650-->
Note that when the radio and receiver are too close (less than 1m) the receiver may be swamped causing spurious alarms, resulting in an annoying "Telemetry Lost" - "Telemetry Recovered" alarm loop.

<!--T:651-->
'''VFR'''

<!--T:652-->
Prior to ACCESS V2.1, RSSI was based on a combination of received signal strength and lost frame rate. Lost frames have now been removed from the RSSI calculation, and added as a new sensor VFR (Valid Frame Rate) to provide a measure of Link Quality.

<!--T:653-->
A warning can be set up to warn you when VFR drops below a minimum value, indicating that the link quality is becoming dangerously low. The default 'Low value warning' is 50.

<!--T:654-->
'''RxBatt'''

<!--T:655-->
Another standard internal sensor is the receiver battery voltage.

<!--T:656-->
'''ADC2'''

<!--T:657-->
Some receivers support a second analog voltage input, which is available in telemetry as sensor ADC2.

<!--T:658-->
===== 2. External sensors =====
The current FrSky telemetry system makes use of FrSky Smart Port sensors. The X and S and later series of telemetry enabled receivers have the Smart Port interface. Multiple Smart Port sensors can be daisy chained together, making the system easy to implement. Most receivers also have either one or both A1/A2 analog input ports, which are useful for monitoring battery voltages, etc.

<!--T:1006-->
==== Telemetry settings ====
Discover and edit sensor options including data logging. When the sensors are discovered they have an individual description for 2.4G or 900M so the sensor values can be used throughout the system. Up to 100 sensors are supported. 

<!--T:660-->
Calculated sensors may be added, including Consumption, Distance and Trip, Multi Lipo, Percent, Power and Custom.

<!--T:661-->
===== Sensors =====
'''Discover new sensors:'''

<!--T:662-->
Once the sensors have been connected, and the radio and receiver have been bound and are powered up, enable ‘Discover new sensors’ to discover new sensors available. A flashing dot in the left column indicates sensor data being received, or the value shows in red if no data is being received. Up to 100 sensors are supported.

<!--T:663-->
During discovery the screen will be automatically populated with all the sensors found.

<!--T:664-->
'''Stop discovery:'''

<!--T:665-->
Move the ‘Discover new sensors’ switch to OFF to stop discovery once the sensors have been discovered.

<!--T:666-->
'''Delete all sensors:'''

<!--T:667-->
This option will delete all sensors so you can start again.

<!--T:668-->
'''Editing and configuring sensors'''

<!--T:669-->
Tap on a sensor, then select 'Edit' from the popup dialog to edit the sensor settings. Alternatively select 'Move Down' to reorder sensors, or 'Delete' to remove it.

<!--T:670-->
'''Value'''

<!--T:671-->
Displays the current sensor reading.

<!--T:672-->
'''ID'''

<!--T:673-->
The ID is the sensor ID. The sending receiver ID is also shown.

<!--T:674-->
'''Name'''

<!--T:675-->
The sensor name, which may be edited.

<!--T:676-->
'''Unit'''

<!--T:677-->
The unit of measurement (dB in this example).

<!--T:678-->
'''Decimals'''

<!--T:679-->
The decimal precision.

<!--T:680-->
'''Range'''

<!--T:681-->
The low and high limits of a range can be set as a fixed value for scaling. This is mostly used when using a telemetry value as a source for a channel. This allows the Range to set to the desired scale. 

<!--T:682-->
'''Write logs'''

<!--T:683-->
When enabled, the sensor data will be logged to the SD card.

<!--T:684-->
'''Sensor lost warning delay'''

<!--T:685-->
When set to ‘Not Set’ will suppress the sensor lost warning. Alternatively, a delay of 1 to 10 seconds may be set, with a default of 5s. This makes it possible to filter out short losses, but the risks must be understood.


<!--T:686-->
'''Reset'''

<!--T:687-->
A source can be configured to reset the sensor.

<!--T:688-->
'''Sensor specific warnings'''

<!--T:689-->
The edit menu may vary for depending on the sensors, for example:

<!--T:690-->
RSSI, VFR, Vert. speed, range etc.

<!--T:691-->
===== Create DIY sensor =====
This option allows you to add a DIY or 3rd party sensor.

<!--T:692-->
'''Value'''

<!--T:693-->
Sensor value being received.

<!--T:694-->
'''Auto detect'''

<!--T:695-->
Auto detect will list all sensors detected on the S.Port/F.Port connection to the receiver. Select your DIY sensor from the list.

<!--T:696-->
'''Physical ID'''

<!--T:697-->
Two character physical ID of the sensor. This will be populated by Auto Detect if selected.

<!--T:698-->
'''Application ID'''

<!--T:699-->
Four character Application ID of the sensor. This will be populated by Auto Detect if selected.

<!--T:700-->
'''Module'''

<!--T:701-->
Allows Internal or External RF module to be selected. This will be populated by Auto Detect if selected.

<!--T:702-->
'''Band'''

<!--T:703-->
Allows 2.4G or 900M to be selected. This will be populated by Auto Detect if selected.

<!--T:704-->
'''RX'''

<!--T:705-->
Allows RX1, RX2 or RX3 to be selected. This will be populated by Auto Detect if selected.

<!--T:706-->
'''Protocol precision/unit'''

<!--T:707-->
Allows the precision for the incoming protocol to be set, from 0 to 3 decimals. It also allows the measurement units to be selected.

<!--T:708-->
'''Display precision /unit'''

<!--T:709-->
Allows the precision to be displayed to be set, from 0 to 3 decimals. It also allows the display measurement units to be selected.

<!--T:710-->
'''Range'''

<!--T:711-->
The low and high limits of a range can be set as a fixed value for scaling. This is mostly used when using a telemetry value as a source for a channel. This allows the Range to set to the desired scale. 

<!--T:712-->
'''Ratio'''

<!--T:713-->
The default 100% ratio may be changed to correct readings being received.

<!--T:714-->
'''Offset'''

<!--T:715-->
The default offset of 0 may be changed to correct readings being received.

<!--T:716-->
'''Write logs'''

<!--T:717-->
When enabled, the sensor data will be logged to the SD card. Logs are enabled by default.

<!--T:718-->
'''Sensor lost warning delay'''

<!--T:719-->
When set to ‘Not Set’ will suppress the sensor lost warning. Alternatively, a delay of 1 to 10 seconds may be set, with a default of 5s. This makes it possible to filter out short losses, but the risks must be understood.

<!--T:720-->
'''Reset'''

<!--T:721-->
A source can be configured to reset the sensor.

<!--T:1007-->
===== Create calculated sensor =====
Calculated sensors may be added, including Consumption, Distance, Trip, Multi Lipo, Percent, Power and Custom.

<!--T:1008-->
=== Checklist ===
The Checklist function provides for a set of Preflight Checks. This is a group of safety features that take effect when powering up the radio and/or loading a model from the model list.

<!--T:725-->
The default checks include radio is in silent mode, failsafe not set, switches and pots check, radio low battery, RTC battery low, etc. The switches check shows the direction the switch should be moved, please refer to the red dots in the warning screen example above.

<!--T:726-->
Please note that contrary to the alert, only the OK or RTN key will skip the Preflight Checks.

<!--T:727-->
Additional checks can be set below.

<!--T:728-->
==== Throttle check ====
To enable throttle check, select the operator to be used. The options are ‘<’ less than, ‘~’ approximately equal, or ‘>’ greater than.

<!--T:729-->
The preflight check will warn you if the throttle stick is outside of the value set in the value parameter

<!--T:730-->
==== Fail-safe check ====
When enabled, it will warn you if Failsafe has not been set for the current model. It is highly advisable to leave this enabled!

<!--T:731-->
==== Switches check ====
For each switch, you can define whether the radio requests that switches to be in the desired predefined positions. If switches have been given user defined names in System / Hardware / Switches Settings, the names will be displayed.

<!--T:732-->
The ‘Load all switches positions’ option can be used to read the desired positions from the 
current switch positions.

<!--T:733-->
The check options are shown above.

<!--T:734-->
==== Function switches check ====
For each function switch, you can define whether the radio requests that switches to be in the desired predefined positions. The options are shown above.

<!--T:735-->
The ‘Load all function switches positions’ option can be used to read the desired positions 
from the current function switch positions.

<!--T:736-->
==== Pots/sliders check ====
Defines whether the radio requests the pots and sliders to be in predefined positions at startup. The desired pot values can be entered for each pot.

<!--T:737-->
The ‘Load all pots positions’ option can be used to read the desired positions from the current pot positions. A careful check must be made to ensure that the automatically selected operators are as desired (i.e. ‘~’ vs ‘<’ or ‘>’).

<!--T:1009-->
=== Logic witches ===
Logical switches are user programmed virtual switches. They aren’t physical switches that you flip from one position to another, however they can be used as program triggers in the same way as any physical switch. They are turned ON and OFF (in logical terms they become True or False) by evaluating the input conditions against the programming for the logical switch. They may use a variety of inputs such as physical controls and switches, other logical switches, and other sources such as telemetry values, mixer values, timer values, gyro and trainer channels. They can even use values returned by a LUA model script (to be supported).

<!--T:739-->
Up to 100 Logic Switches are supported.

<!--T:740-->
There are no default Logic Switches. Tap on the ‘+’ button to add a Logic Switch. 

<!--T:741-->
Once Logic Switches have been defined, tapping on one will bring up the above popup menu, allowing you to edit, add, move, copy/paste, clone or delete that switch.

<!--T:742-->
Selecting 'Move' will bring up arrow keys allowing the logic switch to be moved up or down.

==== Adding logic switches ==== <!--T:743-->

<!--T:744-->
===== Name =====
Allows the Logic Switch to be named.

<!--T:745-->
===== Function =====
The functions available are listed below. Please note that all functions may have normal or inverted outputs. Please also refer to the shared parameters section, as well as the telemetry and comparison of sources sections following the function descriptions below.

<!--T:746-->
===== A ~ X =====
The condition is True if the value of the selected source 'A' is approximately equal (within about 10%) to 'X', a user defined value. 

<!--T:747-->
In most cases, it is better to use the approximately equals function rather than the 'exactly' equals function.

<!--T:748-->
===== A = X =====
The condition is True if the value of the selected source 'A' is 'exactly' equal to 'X', a user defined value.

<!--T:749-->
Care must be taken when using the 'exactly' equals function. For example, when testing if a voltage is equal to a setting of 8.4V, the actual telemetry reading may jump from 8.5V to 8.35V, so the condition is never met and the Logical Switch will never turn on.

<!--T:750-->
===== A > X =====
The condition is True if the value of the selected source 'A' is greater than 'X', a user defined value.

<!--T:751-->
===== A < X =====
The condition is True if the value of the selected source 'A' is less than 'X', a user defined value.

<!--T:1010-->
===== |A| > X =====
The condition is True if the absolute value of the selected source 'A' is greater than 'X',a user defined value. (Absolute means disregarding whether 'A' is positive or negative,and just using the value.)

<!--T:1011-->
===== |A| < X =====
The condition is True if the absolute value of the selected source 'A' is less than 'X', a user defined value. (Absolute means disregarding whether 'A' is positive or negative, and just using the value.)

<!--T:754-->
===== ∆ > X =====
The condition is True if the change in value 'd' (i.e. delta) of the selected source ‘A’ is greater than or equal to the user defined value 'X', within the 'Check interval'. If the 'Check interval' is set to '---', then the check interval becomes infinite.

<!--T:1012-->
===== |∆| > X =====
The condition is True if the absolute value of the change '|d|' in the selected source ‘A’ is greater than or equal to the user defined value 'X'. (Absolute means disregarding whether ‘A’ is positive or negative.). again, if the 'Check interval' is set to '---', then the check interval becomes infinite.

<!--T:756-->
===== Range =====
The condition is True if the value of the selected source 'A' is within the range specified.

<!--T:757-->
===== AND =====
The AND function can have multiple values. The condition is True if all the sources selected in Value 1, Value 2 ... Value(n) are true (i.e. ON).

<!--T:758-->
===== OR =====
The condition is True if at least one or more of the sources selected in Value 1, Value 2 … Value(n) are true (i.e. ON).

<!--T:759-->
===== XOR (Exclusive OR) =====
The condition is True if only one of the sources selected in Value 1, Value 2 … Value(n) are true (i.e. ON).

===== Timer generator ===== <!--T:760-->

<!--T:761-->
The Logical Switch toggles ON and OFF continuously. It switches on for time ‘Duration Active’, and OFF for time ‘Duration Inactive’.

<!--T:1013-->
===== Sticky =====
The Sticky function is latched on (i.e becomes True) when the’Trigger ON condition’ switches from False to True, and holds its value until it is forced to False when the ‘Trigger OFF condition’ switches from False to True. This can be gated by the optional ‘Active Condition’ parameter. This means that if the ‘Active Condition’ is True, then the Logical Switch output follows the Sticky function's condition. However, if the ‘Active Condition’ is False, then the Logical Switch output is also held False.

<!--T:763-->
Note that the Sticky function continues to operate, even if its output is gated by the ‘Active Condition’ switch. As soon as the ‘Active Condition’ switch condition becomes True again, the Sticky function's condition is switched through to the Logic Switch 
output.

<!--T:1014-->
===== Edge =====
Edge is a momentary switch that becomes True for the period specified in 'Duration' when its edge trigger conditions are satisfied.

<!--T:765-->
'''Rising edge option'''

<!--T:766-->
During = '0.0s'

<!--T:767-->
During is in two parts [t1:t2]. With t1 of During = 0.0s and t2= 'Rising Edge', the logic switch becomes True (for the period specified in 'Duration') the instant the 'Trigger On Condition' transitions from False to True.

<!--T:768-->
During >= '0.0s

<!--T:769-->
During is in two parts [t1:t2]. With t1 of During a positive value (say 5.0s) and t2= 'Rising Edge', the logic switch becomes True (for the period specified in 'Duration') 5 seconds after the 'Trigger On Condition' transitions from False to True. Any additional 'spikes' during the t1 period are ignored.

<!--T:770-->
'''Falling edge option'''

<!--T:771-->
During = '0.0s'

<!--T:772-->
During is in two parts [t1:t2]. With During t1=0.0s and t2= '---' (Falling Edge), the logic switch becomes True (for the period specified in 'Duration') the instant the 'Trigger On Condition' transitions from True to False.

<!--T:773-->
During >= '0.0s

<!--T:774-->
During is in two parts [t1:t2]. With t1 of During a positive value (say 3.0s) and t2= '---' (Falling Edge), the logic switch becomes True (for the period specified in 'Duration') when the 'Trigger On Condition' transitions from True to False, having been True for at least 3 seconds.

<!--T:775-->
'''Pulse option'''

<!--T:776-->
During is in two parts [t1:t2]; if values are entered for both t1 and t2, then a pulse is needed to trigger the logic switch.

<!--T:777-->
==== Logic switches – shared parameters ====
The Logic Switches all have a number of shared parameters:

<!--T:778-->
===== Active condition =====
The Logic Switches can be gated by the optional ‘Active Condition’ parameter. This means that if the ‘Active Condition’ is True, then the Logical Switch output follows the Function's condition. However, if the ‘Active Condition’ is False, then the Logical Switch output is also held False. 

<!--T:780-->
Note that the Sticky function continues to operate, even if its output is gated by the ‘Active Condition’ switch. As soon as the ‘Active Condition’ switch condition becomes Trueagain, the Function's condition is switched through to the Logic Switch output.

<!--T:781-->
===== Delay before active =====
This value determines the time for which the Logic Switch conditions have to be True before the Logic Switch output becomes True. (Not relevant to Timer Generator and Edge.)

<!--T:782-->
===== Delay before inactive =====
Similarly, this value determines the time for which the Logic Switch conditions have to be False before the Logic Switch output becomes False. (Not relevant to Timer Generator and Edge.)

<!--T:783-->
===== Min duration =====
Once the Logic Switch becomes True, it will remain True for the duration specified. If the duration is the default 0.0s, the logic switch will only become True for one mixer processing cycle, which is too short to see, so the LSW line will not go bold.

 <!--T:1015-->
'''Note:''' A comment may be added as explanation of its use or function, to aid in understanding. The comment is displayed when a logic switch is added to a value widget.

<!--T:1016-->
==== Logic switches – use with telemetry ====
If the source of a logic switch is a telemetry sensor, if your sensor is active then the Logic Switch will be active.

<!--T:785-->
==== Comparison of sources ====
Normally source (A) is compared to a fixed Value (X). However, comparison of two same�format (i.e. having the same units) sources is allowed. For example, two timers, or two voltages, or two RPM sources may be compared.

<!--T:786-->
==== Option to ignore trainer input  ====
In Logic Switches the sources may have this option set to ignore sources coming from the trainer input. A typical application is where a logic switch is configured to detect movement of the master trainer’s sticks (e.g. Elevator stick) to allow for instant intervention if things go wrong. This option is needed to prevent the student stick inputs from triggering the logic switch.

<!--T:1017-->
=== Special functions ===
Special Functions can be configured to play values, play sounds, etc. Up to 100 Special Functions supported.

<!--T:788-->
There are no default Special Functions. Tap on the ‘+’ button to add a Logic Switch. 

<!--T:789-->
Once Special Functions have been defined, tapping on one will bring up the above popup menu, allowing you to edit, add, move, copy/paste, clone or delete that switch.

<!--T:790-->
Selecting 'Move' will bring up arrow keys allowing the special function to be moved up or down.

<!--T:791-->
Currently the following Special Functions are supported:

<!--T:792-->
* Reset
* Screenshot
* Set fail-safe
* Play track
* Play value
* Haptic
* Writelogs

==== Action: Reset ==== <!--T:793-->

<!--T:794-->
===== State =====
Enable or disable this Special Function.

<!--T:795-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, flight modes, logic switches, trim positions or flight modes.

<!--T:796-->
To select the inverse of for example switch SG-up, if you long press Enter on the switch name and select the Negative check box in the popup the switch value will change to !SG-up. This means the Special Function will be active when switch SG is not in the up position.

<!--T:797-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected.

<!--T:798-->
===== Reset =====
The following categories may be reset:

<!--T:799-->
* Flight data: resets both telemetry and timers
* All timers: resets all 3 timers
* Whole telemetry: resets all telemetry values.

<!--T:800-->
==== Action: Screenshot ====
Will save a screenshot into the location:

<!--T:801-->
SD Card (drive letter)/screenshots/

<!--T:802-->
===== State =====
Enable or disable this Special Function.

<!--T:803-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, flight modes, logic switches, trim positions or flight modes.

<!--T:804-->
To select the inverse of for example switch SG-up, if you long press Enter on the switch name and select the Negative check box in the popup the switch value will changes to !SG-up. This means the Special Function will be active when switch SG is not in the up position.

<!--T:805-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected.

<!--T:806-->
==== Action: Set Fail-safe ====
At the time of writing, this Special Function is still under construction.

==== Action: Play track ==== <!--T:807-->

<!--T:808-->
===== State =====
Enable or disable this Special Function.

<!--T:809-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, logic switches, trim positions or flight modes.

<!--T:811-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected.

<!--T:812-->
===== File =====
Select the wav file to be played.

<!--T:813-->
The file should be located in: SD Card (drive letter)/audio/

<!--T:814-->
Note that the standard audio files are generated by the Google Text-to-Speech tools.

<!--T:815-->
===== Repeat =====
The value may be played once, or repeated at the frequency entered here.

<!--T:816-->
===== Skip on startup =====
If enabled, the file will not be played on startup.

==== Action: Play value ==== <!--T:817-->

<!--T:818-->
===== State =====
Enable or disable this Special Function.

<!--T:819-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, logic switches, trim positions or flight modes.

<!--T:821-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected. 

<!--T:822-->
===== Value =====
Select the source whose value is to be played. The source may be from any of the following:

<!--T:823-->
* Analogs, i.e. sticks, pots or sliders
* Switches
* Logic switches
* Trims
* Channels
* Gyro
* System Clock (Time)
* Trainer
* Timers
* Telemetry

<!--T:824-->
===== Repeat =====
The value may be played once, or repeated at the frequency entered here.

<!--T:1018-->
==== Action: Haptic ====
This Special Function assigns haptic vibration.

<!--T:826-->
===== State =====
Enable or disable this Special Function.

<!--T:827-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, logic switches, trim positions or flight modes.

<!--T:828-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected. 

<!--T:829-->
===== Pattern =====
Sets the pattern of the haptic. Options are single, double, triple, quintuple and very brief.

<!--T:830-->
===== Strength =====
Select the strength of the haptic vibration, between 1 and 10. The default is 5.

<!--T:831-->
===== Repeat =====
The haptic may be executed once, or repeated at the frequency entered here.

<!--T:832-->
==== Action: Write logs ====
Log files are stored in a ‘.csv’ format in the ‘Logs’ folder on the SD card. The files can be read and displayed by OpenTX Companion or any spreadsheet software. LibreOffice is a free open source MS Office compatible package which includes a spreadsheet component. The RTC time and date are logged with the data, and are important to make sense of the data by separating the log data into sessions.

<!--T:833-->
===== State =====
Enable or disable this Special Function.

<!--T:834-->
===== Active condition =====
The Special Function may be Always On, or activated by switch positions, function switches, logic switches, trim positions or flight modes.

<!--T:835-->
===== Global =====
When selecting Global, the special function is added to all existing models and any new model created in the future. If an existing model already has the function the Global function is added as a new function. Turning OFF the Global function on any model removes the function from all models except the current model selected. 

<!--T:836-->
===== Write interval =====
The logs write interval is user adjustable between 100 and 500ms.

<!--T:837-->
===== Sticks/pots/sliders =====
Enables logging of Sticks/Pots/Sliders.

<!--T:838-->
===== Switches =====
Enables logging of Switches.

<!--T:839-->
===== Logic switches =====
Enables logging of Logic Switches.

<!--T:840-->
=== Curves ===
Curves may be used to modify the control response in the Mixers or Outputs. While the standard Expo curve is available directly in those sections, this section is used to define any custom curves that may be required. The 'Add curve' function may also be reached from the Mixer and Outputs edit screens directly.

<!--T:841-->
There are 50 curves available.

<!--T:842-->
There are no default curves (except Expo which is built in). Tap on the ‘+’ button to add a new curve. Tapping on a list of curves brings up a dialog allowing you to Edit, Move, Copy, Clone or Delete the highlighted curve. You can also add another curve.

<!--T:843-->
The initial screen allows you to name your curve, and to select the curve type.

<!--T:844-->
The available curve types are:

<!--T:845-->
==== EXPO ====
The default exponential curve has value of 40. 

<!--T:846-->
A positive value will soften the response around 0, while a negative value will sharpen the response around 0. Softening the response around mid stick helps to avoid over controlling the model, especially for beginners.

<!--T:847-->
===== Function =====
The following mathematical function curves are available:

<!--T:848-->
'''x > 0'''

<!--T:849-->
If the source value is positive, then the curve output follows the source. If the source value is negative, then the curve output is 0.

<!--T:850-->
'''x < 0'''

<!--T:851-->
If the source value is negative, then the curve output follows the source. If the source value is positive, then the curve output is 0.

<!--T:852-->
'''|x|'''

<!--T:853-->
The curve output follows the source, but is always positive (also called ‘absolute value’).

<!--T:854-->
'''f > 0'''

<!--T:855-->
If the source value is negative, then the curve output is 0. If the source value is positive, then the curve output is 100%. 

<!--T:856-->
'''f < 0'''

<!--T:857-->
If the source value is negative, then the curve output is -100%. If the source value is positive, then the curve output is 0. 

<!--T:858-->
'''|f|'''

<!--T:859-->
If the source value is negative, then the curve output is -100%.

<!--T:860-->
If the source value is positive, then the curve output is +100%.

<!--T:861-->
===== Custom =====
'''Points count'''

<!--T:862-->
The default custom curve has 5 points. You may have up to 21 points on your curve.

<!--T:863-->
'''Smooth'''

<!--T:864-->
If enabled a smooth curve is created through all points.

<!--T:865-->
'''Easy mode = ON'''

<!--T:866-->
Easy mode has equidistant fixed values on the X axis, and only allows the Y coordinates for the curve to be programmed.

<!--T:867-->
'''Points config'''

<!--T:868-->
With Easy mode ON, only the Y coordinates may be configured (see example above).

<!--T:869-->
'''Easy mode = OFF'''

<!--T:870-->
Easy mode has equidistant fixed values on the X axis, and only allows the Y coordinates for the curve to be programmed.

<!--T:871-->
'''Points config'''

<!--T:872-->
With easy mode OFF, both the X and Y coordinates may be configured, (see example above). Note that the -100% and +100% X coordinates for the curve end-points cannot be edited, because the curve must cover the full signal range.

<!--T:873-->
=== Trainer ===
The trainer function is OFF by default.

==== Trainer mode = master ==== <!--T:874-->

<!--T:875-->
===== Link mode (Wireless OFF/ON) =====
The trainer link can be either via cable or wireless (Bluetooth). The cable should be a 3.5mm mono audio lead.

<!--T:876-->
===== Mode =====
Allows selection between Normal Speed and High Speed for the Bluetooth link. For lower latency the High Speed setting should be used if both radios support it.

<!--T:877-->
===== Local name =====
This is the local BT name that will be displayed in devices being connected. The default name is FrSkyBT, but may be edited here.

<!--T:878-->
===== Local address =====
This is the local Bluetooth address of the radio.

<!--T:879-->
===== Dist address =====
Once a Bluetooth device has been found and linked, the remote device's Bluetooth address is displayed here.

<!--T:880-->
===== Search address =====
The Search Devices button will be available if the Trainer Mode is Master.

<!--T:881-->
Tap on 'Search Devices' to put the radio into BT search mode. Found devices are listed in a popup dialog with a request to select a device. Select the BT address that matches the radio to be used as training mate.

<!--T:882-->
===== Active condition =====
Control of the model can be transferred to the student radio by a switch or button, a function switch, logic switch, trim position, or flight mode.

<!--T:883-->
Up to 16 controls may be transferred from the student radio to the master radio when the 'Active Condition' set above is active.

<!--T:884-->
Tap on each channel to configure it individually.

<!--T:885-->
'''Active condition'''

<!--T:886-->
Each individual slave channel can also be controlled by the selected source. So for example the student’s elevator input can be disabled during a session.

<!--T:887-->
'''Mode'''

<!--T:888-->
OFF: disables the channel for trainer use.

<!--T:889-->
Add: selects additive mode, where both master and slave signals are added so both teacher and student can act upon the function.

<!--T:890-->
Replace: replaces the master radio's control with the student's, so the student has full control while the 'Active Condition' is active. This is the normal mode of use.

<!--T:891-->
'''Percent'''

<!--T:892-->
Normally set to 100%, but can be used to scale the Slave input.

<!--T:893-->
'''Destination'''

<!--T:894-->
Maps the slave radio's channel to the corresponding function.

<!--T:895-->
==== Option to ignore trainer input  ====
In Logic Switches the sources may have this option set to ignore sources coming from the trainer input. A typical application is where a logic switch is configured to detect movement of the master trainer’s sticks (e.g. Elevator stick) to allow for instant intervention if things go wrong. This option is needed to prevent the student stick inputs from triggering the logic switch.

<!--T:896-->
===== Trainer mode = slave =====
'''Link mode (Wireless OFF/ON)'''

<!--T:897-->
The trainer link can be either via cable or wireless (BT). The cable should be a 3.5mm mono audio lead.

<!--T:898-->
'''Local name'''

<!--T:899-->
This is the local BT name that will be displayed in devices being connected. The defaultname is FrSkyBT, but may be edited here.

<!--T:900-->
'''Local address'''

<!--T:901-->
This is the local Bluetooth address of the radio.

<!--T:902-->
'''Dist address'''

<!--T:903-->
Once a Bluetooth device has been found and linked, the remote device's Bluetooth address is displayed here.

<!--T:904-->
'''Channels range'''

<!--T:905-->
Selects which channel range is transferred to the master radio.

<!--T:1019-->
=== Device config ===
Device config contains tools for configuring devices like sensors, receivers, the gas suite, servos and video transmitters.

<!--T:907-->
<s>[The following devices are currently supported:</s>

<!--T:908-->
* <s>Airspeed</s>
* <s>Current</s>
* <s>SBEC</s>
* <s>Gas Suite</s>
* <s>GPS</s>
* <s>Lipo voltage</s>
* <s>RB 30/40</s>
* <s>RPM</s>
* <s>SxR</s>
* <s>SxR calibration</s>
* <s>Variometer</s>
* <s>VS600 video transmitter</s>
* <s> XAct servos</s>
* <s>Pressure</s>
* <s>Temperature]</s>

<!--T:909-->
Please refer to the device's manual for further details.

<!--T:910-->
Please note that the ETHOS Device Config screen lets you change Physical IDs and Application IDs. If you have more than one device that have the same function, you would need to connect them one at a time, discover them in Telemetry / Discover New Sensors, then in Device Config change the Physical ID and Application ID, and then go back and rediscover them with the new ID. Please refer to the Telemetry section.

<!--T:911-->
== Configure screens ==
The main views are customized and configured by the Configure Screens top level function, which is accessed by the ‘Multiple Screens icon’ in the bottom menu bar.

<!--T:912-->
The main views are user configurable by selecting widgets to display desired information such as telemetry and radio status etc. There can be up to eight user defined screens. The user can select from thirteen different screen widget configurations for each new screen with up to nine cells for displaying widgets. The widgets can display telemetry values, but also values from seventeen other different categories. Once the screens are configured with widgets they can be accessed using a touch swipe gesture or navigation controls. The top and bottom bar with their active icons remain displayed on all screens. 

<!--T:913-->
Touching the ‘Multiple Screens icon’ in the middle of the main screen bottom bar brings up the first screen for configuring screens.

<!--T:914-->
Touch on ‘Screen1’ to configure the first default screen.

<!--T:915-->
=== Configuring the main screen ===
By default the first screen has a large widget on the left to display the model’s bitmap, and three widgets on the right to display the three timers. These widgets may be reconfigured to display other parameters, or the entire screen layout can be replaced by a newly defined screen with a different number of cells or cell layout.

<!--T:916-->
Each widget displays the widget type at the top left. For configurable widgets the source is shown at the bottom left of the widget, which may be changed by touching the down arrow. Once the source has been selected, the widget may be configured by touching the ‘Configure Widget’ button.

<!--T:917-->
If the widget is not configurable, only a ‘Change Widget’ button is displayed.

<!--T:918-->
Touching the “Change Widget’ button brings up a widget category dialog. Custom Lua widgets will also appear in the list. 

==== Standard widgets ==== <!--T:919-->

<!--T:920-->
==== Model bitmap ====
Used to display the selected bitmap.

<!--T:921-->
===== Value =====
The Value widget simply displays the value of the selected source. 

<!--T:922-->
===== Timer logs =====
The timer logs provide a log of timer values. The timer values are written when the timeris reset.

<!--T:923-->
Long press on the widget to Clear Logs, Timer(n) Edit, Timer(n) Reset or configure the widget or screens.

<!--T:924-->
===== GPS map =====
This widget supports a GPS map display. Please refer to the X20 Ethos thread on rcgroups for more details, especially post #8854.

<!--T:925-->
===== LiPo =====
The Lipo widget will display Lipo voltage information from sensors such as FLVSS.

<!--T:926-->
If the lowest cell voltage is below the ‘Low Voltage’ threshold, the voltages are displayed
in red.

<!--T:927-->
===== Channels =====
The Channels widget allows up to 8 channels to be displayed in bar chart format, with either horizontal or vertical bars.

<!--T:928-->
The example above shows two Channels widgets, the left one showing 4 channels vertically, while the right one shows 8 channels horizontally.

<!--T:929-->
===== Line chart =====
The Line Chart widget allows the selected source to be charted.

<!--T:930-->
===== Log period =====
The log period can be set. Using a 500ms period, the chart will cover about 6 minutes before starting to scroll off the page, while 1s will cover about 12 minutes.

<!--T:931-->
===== Flexible range =====
If Flexible Range is turned on, then the vertical axis will be scaled according to the Min and Max settings. In the example above, the top widget has been set for Flexible Range and the chart shows a source swing of +26% to -22% so far.

<!--T:932-->
===== Min/Max =====
If Flexible Range is turned OFF, then the vertical axis will be scaled according to the to suit the input. In the example above, the bottom widget has a fixed range of -100% to +100%.

<!--T:933-->
Once a choice has been made, a ‘Configure Widget’ button appears, allowing further configuration of the widget.

<!--T:934-->
=== Adding additional screens ===
Tap on the ‘+’ button next to ‘Screen1’ to add an additional screen.

<!--T:935-->
You can select from 13 different layouts (including full screen and a choice of two home screens) having up to 9 widgets. These can then be configured as for screen 1.

<!--T:936-->
Screens may be re-ordered or even deleted. The screen editing dialog is invoked by tapping on Screen1, or Screen2, etc.

<!--T:937-->
=== Adding custom widgets ===
Custom widgets are typically lua scripts which normally come in the form of a single ‘main.lua’ file, which is commonly kept in a subfolder with a name that suggest its functionality. This subfolder should be copied to the ‘scripts’ folder on the SD card. The widget will be automatically registered at startup. Configure Screens can then be used to configure the widget like any other.

== Lua scripts == <!--T:938-->

=== Ethos suite === <!--T:939-->

<!--T:940-->
==== Overview ====
The Ethos Suite PC application runs on a Windows PC or Mac and connects to FrSky radios that are running the ETHOS operating system. Ethos Suite connects to the radio via a USB cable.

<!--T:941-->
Once connected to the radio the current release of ETHOS SUITE can do the following things:

<!--T:942-->
* Determine the radio type, ID, and the versions of the firmware, the files in Flash memory, and the SD card files.
* Change the mode of the radio from running in bootloader mode to starting and running Ethos on the radio, with the option of switching back again.
* With the current radio status information displayed, Ethos Suite provides the user with selections for updating to the most current and correct firmware and files. It then downloads and installs them automatically. The user can select to update the outdated components, to update all, or to update the radio firmware or the Flash files or the SD card contents individually.
*  Using the Model Manager a backup of the models on the radio can be saved to disk, or a previously saved backup may be restored to the radio. Models are not backwards compatible, so the older model files have to be restored from the PC when downgrading to older firmware.
* The FRSK Flasher can use the radio as a proxy to flash the internal module directly or any sensor, servo, or receiver.
* Flash the radio bootloader in DFU mode (power OFF connection).
* Convert images to ETHOS format.
* Convert audio files to ETHOS format.

<!--T:943-->
* There is a Repair Tool for the X18/S, TW Lite and XE radios. If your radio cannot read from NAND or the settings cannot be saved, this tool can be used to reformat the internal storage.
*  Eject USB connections.
* At startup there will be a notification if there is an ETHOS SUITE update available. 

<!--T:944-->
Installation takes place. when Suite is exited.

<!--T:945-->
Note that besides the Tools, SUITE offers 3 modes of operation with the radio.

<!--T:946-->
===== Radio in bootloader mode =====
The Radio tab is available for checking and updating the radio firmware and the Flash and SD card files to the latest versions.

<!--T:947-->
The Model Manager tab is available for making a backup of the radio, or to restore a saved backup to the radio.

<!--T:948-->
===== Radio in Ethos mode =====
In this mode Ethos Suite can use the radio as a proxy to flash the internal module directly or any sensor, servo, or receiver. The FRSK Flasher tab manages these operations.


<!--T:949-->
===== Radio in DFU mode =====
The Radio is connected in power OFF mode, and the DFU Flasher tab is used for flashing the bootloader. This is required if for example the radio firmware has been corrupted and the radio no longer powers up.

==== Procedure for migrating to Ethos suite ==== <!--T:950-->

<!--T:951-->
* Ensure that you are on at least Ethos version 1.1.4, the minimum version needed to flash the new Ethos Suite compatible bootloader (FRSK format) from the File Manager on the radio. If not, you will need to manually update to 1.1.4 to be able to migrate to Ethos Suite for automated updates.
* Make a backup your SD card (it’s advisable to copy all of it to a folder on your computer).
* Download the zip file for the latest bootloader from https://github.com/FrSkyRC/ETHOS-Feedback-Community/releases (currently the bootloader is 1.4.3, please refer to the 1.4.3 release for the file) for your radio, and unzip it.
* Power the radio on in bootloader mode (hold the enter key down, keep it down and then press power ON) and connect the system to the PC with a data USB cable.
* Copy the bootloader to a folder on your SD card (normally the Firmware folder), then eject the drives and disconnect the radio from the PC.
* Start the radio, go to System / File Manager, tap the bootloader.frsk file you have just copied and select the ‘Flash bootloader’ option.
* Download and install the Ethos Suite. You should now be able to follow the sections below to update your radio firmware and the Flash and SD card files to the latest versions, and make use of the other Ethos Suite features.
* Please note that you may need to rename the bitmaps/user folder on the SD card to bitmaps/models if ETHOS Suite does not do it for you. This is the folder where user bitmaps are stored.

== Conclusion == <!--T:1020-->

<!--T:1021-->
=== Principles of safe operation ===
Operating the models can be dangerous if you do not follow the appropriate safety guidelines. Here are some of the most important recommendations to help ensure safe operation.

<!--T:1022-->
* Before taking off, make sure the model responds properly to the gimbal movements on the transmitter. Also make sure all switches and other controls are functioning properly. If you find any problems, do not fly the model until all functions are working properly.
* Never fly in rain, strong winds or at night. Water can cause failure or improper operation and impair the control of the model, with the risk of a crash.

<!--T:1023-->
* Never turn off the power switch in flight when the model‘s engine is running or the battery is connected. In this case, control of the model will be impossible, and the model will crash. Even if you turn the switch back on, normal operation will not resume until the internal transmitter and receiver initialization processes are completed.
* Do not start the internal combustion engine or electric motor while wearing the neck strap. The strap can be caught by a spinning propeller, rotor, etc. and cause serious injury.
* Never fly in range check mode In this mode, the transmitter operates at reduced power and a crash could occur.
* Do not fly if you are physically or mentally indisposed, as this can be dangerous to yourself and others. Also, never fly under the influence of alcohol, narcotics or drugs affecting your senses.
* Do not fly near airports, near or over people, near residential buildings, schools, hospitals, or other places where people congregate, near high voltage power lines, tall buildings and structures, or communication facilities.
* If you place the transmitter on the ground in preparation for flight, do not place it in an upright position. The transmitter may tip over, the controls may become misaligned, and the propeller or rotor may spin unexpectedly and cause injury.
* Do not touch internal combustion engines, electric motors or controllers during or immediately after operation. These devices can become very hot during operation.
* For safety reasons, always fly with the model in line of sight at all times. Getting behind buildings or other large objects will not only cause you to lose sight of the model, but the obstruction will prevent the RF signal from the transmitter from propagating and cause you to lose control of the model.
* Always set fail-safe emergency rates for safety. Take special care to set the throttle to neutral in case of an emergency.
* Always check the charge level of the transmitter and receiver batteries before each takeoff. Low voltage will cause loss of control of the model and a crash.
* At the beginning of each flight day, check the operation of all control surfaces and perform a range check. If using the Trainer function, check that the model responds properly to both teacher and student transmitter controls. Even an incorrect setting of a single transmitter or model function can cause a crash.
* Before turning on the transmitter: 1. Always pull the throttle control all the way down (to neutral). 2. Turn the transmitter on first, then the receiver.
* Before turning off the transmitter after the internal combustion engine or electric motor has stopped (is in a condition where it cannot start again): 1. Turn off the receiver power switch. 2. Then turn off the transmitter power switch. If you turn the power on/off in reverse order, the propeller or rotor may spin unexpectedly and cause injury. Also, follow the above order when setting fail-safe emergency rates.
* When setting the transmitter, turn the engine off/shut down unless its operation is necessary for the setting. In the case of an electric motor, disconnect its cables. Use extra caution when setting the transmitter while the motor is running. Ensure that the model is properly secured and cannot come into contact with anyone or anything. An unexpected increase in RPM can cause serious injury.

<!--T:1024-->
=== Warranty and post-warranty service ===
All '''KAVAN''' electronic products are covered by a 2-year warranty covering all manufacturing defects and faults. When making a claim within the warranty period, please always present a copy of the proof of purchase with the product and provide the service personnel with as detailed and complete information as possible about the defect found, your usage and other information that will facilitate the assessment of the claim and speed up its settlement. Please make your claim at the shop where you purchased the product. If this is not possible, you can directly contact '''KAVAN Europe s.r.o.''':

<!--T:1025-->
'''KAVAN Europe s.r.o.''' | '''Doubravice 110, 533 53 Pardubice''' | '''Czechia''' | '''+420 466 260 133''' | '''info@kavanrc.com'''

<!--T:1026-->
=== Warranty and limitation of liability ===
As the manufacturer of this product, we have no control over your compliance with these instructions when wiring and installing the RC set into your model. Likewise, we have no control over the way you build, operate and maintain the RC set parts. For this reason, KAVAN must disclaim all liability for any loss, damage or financial cost that is caused by the improper use or operation of products imported by us, or that is in any way connected with such activity.

<!--T:1027-->
Except as otherwise provided by law, KAVAN‘s obligation to pay compensation shall (regardless of the legal arguments asserted) be limited to the purchase price for those KAVAN products that were directly involved in the event that caused the damage. This does not apply if the manufacturer has been judicially obliged to make unlimited compensation on the basis of proven wilful or gross negligence. We warrant that our products are in compliance with current legal provisions. The warranty does not cover failures and defects caused by:

<!--T:1028-->
* Misuse or improper use.
* Delayed, improper or no maintenance, or maintenance performed by unauthorized service.
* Incorrect wiring.
* Use of accessories not approved or recommended by KAVAN Europe s.r.o.
* Modifications or repairs not carried out by an authorised KAVAN Europe s.r.o.
* Inadvertent or deliberate damage.
* Normal wear and tear.
* Operation of the equipment outside the operating limits specified in the specification

<!--T:1029-->
KAVAN Europe s.r.o. warrants that this product is free from defects in both material and workmanship at the time of sale. KAVAN Europe s.r.o. also reserves the right to change or modify this warranty without notice. The equipment is subject to continuous improvement and refinement - the manufacturer reserves the right to change the design without notice.

<!--T:1030-->
This warranty certificate entitles you to a free warranty repair of the product supplied by KAVAN Europe s.r.o. within a period of 24 months. The warranty does not cover natural wear and tear due to normal use, as this is a product for modelling use, where the individual parts operate under much higher loads than normal toys are subjected to.

<!--T:1031-->
The warranty also does not cover any part of the equipment that has been improperly installed, roughly or improperly handled, or damaged in an accident, or any part of the equipment that has been repaired or altered by an unauthorized person (this includes the application of any waterproof sprays/coatings by the user). Like other fine electronics products, do not expose this equipment to high temperatures, low temperatures, moisture, dusty environments, violent mechanical shocks and impacts. Do not leave it in direct sunlight for extended periods of time.

<!--T:1032-->
Please claim warranty repairs from the shop where you purchased the set.

<!--T:1033-->
=== Recycling (European Union) ===
[[File:WEEE.svg|right|frameless|50x50px]]
Electrical equipment bearing the crossed-out bin symbol must not be disposed of in normal household waste, instead, it must be taken to a specialised collection and recycling facility. In EU (European Union) countries, electrical equipment must not be disposed of in normal household waste (WEEE - Waste of Electrical and Electronic Equipment, Directive 2012/19/EU). You can take unwanted equipment to your nearest collection or recycling centre. The equipment will then be disposed of or recycled safely free of charge. By handing in your unwanted equipment, you can make an important contribution to protecting the environment.

<!--T:1034-->
=== EU Declaration of conformity ===
[[File:CE.svg|right|frameless|50x50px]]
'''KAVAN Europe s.r.o.''' hereby declares that the radio equipment type: '''V20''' and other equipment supplied with it are in compliance with the Directive 2014/53/EU. The full text of the EU Declaration of Conformity is available at the following website: <nowiki>http://www.kavanrc.com/doc</nowiki>. This 2.4GHz radio equipment can be used without prior registration or individual approval in all countries of the European Union.
</translate>