Spirit System Manual - Recent changes [en]

Main Page/en

FuzzyBot — Sun, 02 Aug 2026 10:29:46 GMT

Importing a new version from external source

Manual/en

FuzzyBot — Sun, 02 Aug 2026 10:29:44 GMT

Importing a new version from external source

Main Page/en

FuzzyBot — Sun, 02 Aug 2026 10:29:40 GMT

Importing a new version from external source

Spirit Wave Specs/en

FuzzyBot — Sun, 02 Aug 2026 10:29:37 GMT

Importing a new version from external source

Altitude Hold/en

FuzzyBot — Sun, 02 Aug 2026 10:29:34 GMT

Importing a new version from external source

New page

<languages/>

== Altitude Hold ==

For automatic maintaining altitude of the model you can use this function. It works with Spirit 3, Spirit W3, Spirit GT and Spirit GTR without need of connecting any other peripheral. Operation is based on internal Pressure sensor that can sense altitude during flight.

=== How it works ===

The model will try to maintain altitude at which the feature was engaged. It can work in a normal flying mode and any Stabi function.
Pilot can safely change the altitude by collective pitch movements anytime. If without movement, the altitude is maintained.
This feature can work also upside down in the same way.

The feature will not change anything else than collective pitch.

To enable this feature it is required to set '''F: Spirit Altitude Hold''' at the General/Channels - right side.

=== Usage ===

The feature can be engaged at any given time by a switch from your radio. It is important to decide in which way the feature will be engaged as there are two options.

# To engage with Stabi function - in this case the feature is engaged when programmed Stabi function is engaged. This mean you do not need to assign any other switch than when used for e.g. Stabilisation mode
# To engage with assigned GeoLink channel - it is required to assign ''F: GeoLink Altitude Hold'' function in the ''General/Channels'' to an available channel.

=== Modes ===

There are following modes available, depending on channel value.
In the Channels window you will be able to see Function as '''On (1)''', '''Off''' and '''On (2)''' which is corresponding to 100%, 0% and -100% channel value.

When '''On (1)''' is displayed it mean that altitude in which the feature was engaged will be held. Pilot is still able to change Collective Pitch, but in a limited manner. Collective Pitch reaction will be slower than in a normal flight mode.

When '''On (2)''' is displayed it mean that altitude in which the feature was engaged will be held. Pilot is unable to change Collective Pitch by pitch stick. So that Collective Pitch steering is fixed and is changed only by Barometer in order to hold right altitude.

== Safety ==

Although Spirit unit is automatically changing Collective Pitch in this mode, it is always required that pilot have full control over R/C model. Pilot must always watch the model while holding radio transmitter and to not allow flying anywhere where a damage could occur. All functions that the module provide can be turned off at any time and with no delay so that pilot can steer the model normally. Improper operating conditions can lead to a failure of the system.

Altitude Hold can be used for the most 3D maneuvers, however holding precision is very dependent on model, Spirit mounting position and ambient pressure variation. The best precision can be obtained so that after each maneuver pilot is waiting until altitude is stabilized. If maneuver takes longer time while Collective Pitch is changing often, measuring precision is significantly lower.
 
{{Quote|'''The user takes full responsibility for any damage or injury caused while flying an R/C model equipped with one of our devices. The manufacturer can neither guarantee nor control the conditions in which the unit is being used.'''}}

Castle Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:29:34 GMT

Importing a new version from external source

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 10:29:24 GMT

Importing a new version from external source

SpiritW1 Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:29:07 GMT

Importing a new version from external source

New page

<languages />
<div id="up"></div>
__NOTOC__
=Telemetry=
Spirit W1 and Spirit W3 are equipped with 2 separate inputs for Spirit Telemetry sensors.
These sensors are compatible also with external Spirit RX receivers.

Available telemetry ports:
* '''T1'''
* '''T2'''

Please note these ports are not used for ESC telemetry or GeoLink module.

{{Quote| Spirit W1/W3 is equipped also with X pin at T2/RPM/X port. This pin is used internally for communication with built-in receiver. '''When using Spirit RX receiver nothing should be connected to X pin.'''}}


== Telemetry Sensor Wiring ==

=== T1 port ===

Connect Sensor or Expander cable directly without any change.

[[File:spiritw1-t1.jpg|class=smallwidth]]

=== T2 port ===

Connect Spirit Sensor cable in so that RED/BROWN wires are at the AUX port (or any other free powering port) and ORANGE wire at the bottom T2 pin.
In case of lack of free ports, please use an Y-cable.

{{Info|[[File:Info.png]] Original connector must be modified so that two servo connectors are used.}}


[[File:spiritw1-t2.jpg|class=smallwidth]]

== Telemetry Sensor Data ==

You can set display Sensor Data at the Main screen by opening adding '''Widgets'''.

[[File:wave-widgets.png|480px]] [[File:wave-widgets-example.png|480px]]

== Spirit Telemetry ==

Besides Spirit Telemetry sensors you can also utilize the [[ESC telemetry|ESC Telemetry]], [[GeoLink|GeoLink module]] and Spirit telemetry variables.

This mean you can interface your ESC and display telemetry data such as Battery Voltage, Current, Consumed Capacity, Temperature, RPM.

For more details about ESC telemetry please visit linked guide.

Similarly you can install GeoLink for measuring GPS position, Speed and other variables.

Spirit Wave Specs/en

FuzzyBot — Sun, 02 Aug 2026 10:29:02 GMT

Importing a new version from external source

Jeti Integration/en

FuzzyBot — Sun, 02 Aug 2026 10:28:59 GMT

Importing a new version from external source

HobbyWingV5 Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:28:54 GMT

Importing a new version from external source

Jeti Integration/en

FuzzyBot — Sun, 02 Aug 2026 10:28:51 GMT

Importing a new version from external source

SpiritW1 Binding/en

FuzzyBot — Sun, 02 Aug 2026 10:28:49 GMT

Importing a new version from external source

New page

<languages/>

=4 Binding Procedure =

In order to Bind Spirit W1 or Spirit W3 with your Wave radio use supplied Bind plug.

#Insert '''Bind plug''' at the '''SYS port''' and connect Power supply to the Spirit W1/W3 unit. You can connect BEC or 1-3S Battery at the '''THR, AUX, T1''' ports.
#Spirit W1 unit will start to blink with the Status LED periodically.
#Then power up your Wave radio.
#Radio will automatically bind to the receiver when using new Model profile. You can also Bind anytime manually as described in the section above.
#After successfull binding Spirit unit will stop blinking and will initialize. Then you can remove the Bind plug.

[[File:spritW1-bind.jpg|class=halfwidth|center]]

== Manual Binding ==
You can Bind manually by going to the '''Model/Receiver''' menu.
Press the '''Bind button''' after powering up Spirit W1/W3 with a Bind plug.

[[File:wave-bind.png|480px|center]]

<div class=noprint>
----
{|style="width: 100%;color: white;"
|-
| style="width: 33%;"| [[SpiritW1 Wiring|← Wiring]]
| style="width: 33%;text-align:center;"| [[#up|↑Up↑]]
| style="text-align:right;" | [[SpiritW1 Setup|Configuring from Radio →]]
|}
----
</div>

Jeti Integration/en

FuzzyBot — Sun, 02 Aug 2026 10:28:48 GMT

Importing a new version from external source

OMP Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:28:47 GMT

Importing a new version from external source

Spirit Wave ESC Integration/en

FuzzyBot — Sun, 02 Aug 2026 10:28:46 GMT

Importing a new version from external source

New page

Spirit Wave is able to configure supported ESCs directly through Modern User Interface.
This mean that not only Telemetry values can be seen at Wave Display but additionally pilot can access also particular ESC settings and change them without any additional programming device.

== Supported ESCs ==

Supported ESCs are subject of a firmware version. With following updates more ESCs will be suppported.

Presently following ESCs are fully supported:

* YGE LVT/HVT series
* HobbyWing v5 series
* XDFly
* Scorpion Tribunus

== Wiring ==

=== YGE LVT/HVT ===

Wiring is identical as for a standard ESC telemetry support with Spirit units. Please visit [[YGE_Telemetry|YGE Telemetery]] page.

'''Requirements:'''
* ESC has to be configured for YGE protocol.

=== HobbyWing v5 ===

Wiring is identical as for a standard ESC telemetry support with Spirit units. Please visit [[HobbyWingV5_Telemetry|HobbyWing v5 Telemetery]] page.

'''Requirements:'''
* Spirit Wave firmware: 1.0.20+
* Spirit firmware: 3.7.3

=== XDFly ===

Wiring require a single cable between '''SAT1 port''' and '''RX pin''' of the ESC.

'''Requirements:'''
* ESC firmware has to be the latest version

== Setup ==

For enabling the Integration you have to enter '''Model - ESC - Type''' page.

[[File:wave-esc-setup.png|550px]] [[File:wave-esc-setup2.png|550px]]

After Saving the settings you can repower the Spirit unit and from then ESC Integration is ready to use.

== Usage ==

For accessing ESC parameters you have to enter '''Model - ESC - ESC Setup''' page. This page is available only if ESC Integration is really working.
This mean ESC Setup might not work because of:
* Wrong Wiring
* Wrong (old) ESC firmware
* Wrong telemetry protocol configured in the ESC.

If you can see no ESC telemetry values then this integration will not work.

=== ESC Setup ===

Parameters can be easily accessed as part of the Wave User Interface without requirement of installing any special tool.

Following screenshots were recorded from HobbyWing v5 configuration interface.

[[File:wave-esc-setup-hw5.png|550px]]

[[File:wave-esc-setup-hw52.png|550px]] [[File:wave-esc-setup-hw53.png|550px]]

[[File:wave-esc-setup-hw54.png|550px]] [[File:wave-esc-setup-hw55.png|550px]]

Castle Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:28:40 GMT

Importing a new version from external source

Spirit Wave Safety/en

FuzzyBot — Sun, 02 Aug 2026 10:28:18 GMT

Importing a new version from external source

Spirit Wave Trims/en

FuzzyBot — Sun, 02 Aug 2026 10:28:16 GMT

Importing a new version from external source

New page

=Channel Trims=
__NOTOC__
Spirit Wave brings brand new way for Trimming your Model.
This method is easy, safe and can be used In-Flight.

Since Wave is designed for all kind of models whereas only some require to Trim. You can access the Trimming feature from the '''Trim Widget'''.
Trim Widget is accessible for all models except these equipped with Spirit unit and Helicopter firmware. This is because Spirit unit does not require any trimming when used with a helicopter model.

*This allows Trimming '''only at a time you really want''', making it safer comparing to a Physical Trims.
*Morever there is '''no need to take your fingers off''' the sticks, allowing full control without interruption.
*Lastly, this trim method allow a '''Variable Trim Rate''' unlike a Physical Trims. The bigger trow is used, the bigger trim rate is picked.

[[File:wave-widget-trim.png|550px]]

== Trim ==

General Trimming Process can be described in the following steps:
#Engaging the Trim Mode
#Moving with a Sticks in a direction you wish to trim.
#Disengaging the Trim Mode

=== Engaging ===

You can engage the Trim Mode in a several different ways, however two different methods are available:
*Engaging with a Touch
*Engaging with assigned Input

==== Touch ====

This method require entering Trim Widget and touching designated Area for as long as needed. When a finger is released Trim Mode is disengaged.

[[File:wave-widget-trim-touch.png|550px]]

==== Input ====

Alternative method is using assigned Input such as Switch, Potentiometer, Slider or Tilting to engage the Trim Mode. This method allows to Trim at any moment when Radio is powered on as soon as the Input is set to an Active position.

[[File:wave-widget-trim-input.png|550px]]

As recommended input for engaging the Trim Mode a Momentary Switch can be used.

=== Options ===

To minimize unwanted Trimming you can further select which functions can be used. For example if you know only Rudder and Aileron trims are required you can safely control Elevator and Throttle even when the Trim Mode is active.

[[File:wave-widget-trim-opt.png|550px]]

=== Reset ===

You can reset configured Trims for each channel individually in the '''Model - Channels - Subtrim'''.

[[File:wave-widget-trim-reset.png|550px]]

JR XBUS/en

FuzzyBot — Sun, 02 Aug 2026 10:28:04 GMT

Importing a new version from external source

New page

JR XBUS is transmission protocol supported by JR receivers.
It is supported by all recent Spirit units.

== Wiring ==

'''RUD port''' at the Spirit side - '''XBUS''' port at the RX side.

== Spirit Settings ==

Now you are ready to power up the unit. If your Power supply is not connected yet, we recommend to connect it to the AUX1, AUX2 and/or CH0 port.
Before you can utilize the Spektrum integration connection, it is important to set the '''JR XBUS A''' receiver type in the General tab of the software. Please start the Spirit Settings and change the receiver type as displayed on the photo.
Then save the settings (e.g. by ''CTRL+S'') or the ''Backup tab/Unit - Save'' and restart the unit.

[[File:XBUS-settings.png|thumb|center]]

OMP Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 10:28:04 GMT

Importing a new version from external source

Jeti Integration/en

FuzzyBot — Sun, 02 Aug 2026 09:06:38 GMT

Importing a new version from external source

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 09:06:37 GMT

Importing a new version from external source

Spirit Wave Binding/en

FuzzyBot — Sun, 02 Aug 2026 09:06:22 GMT

Importing a new version from external source

New page

__NOTOC__
<languages/>
= Binding Procedure =

Binding is two side operation, in which Radio and Receiver is put into the Binding mode at the same time. Both will learn how to talk to each other and from this time they will transmit both channel data, telemetry and allow remote configuration. Bind Date are stored at both sides. Model that is created in your Radio is matched with one specific receiver.

== Spirit W1 ==
In order to Bind Spirit W1 with your Wave radio use supplied Bind plug.

{{Info|[[File:Info.png]] If Spirit W1 is new (no Bind Data available) a Bind Plug is not required and you can continue with the following section '''Binding with Wave'''.}}


#Insert '''Bind plug''' at the '''SYS port''' and connect Power supply to the Spirit W1 unit. You can connect BEC or 1-3S Battery at the '''THR, AUX, T1''' ports.
#Spirit W1 unit will start to blink with the Status LED periodically.
#Perform binding according following '''Binding with Wave''' section.

[[File:spritW1-bind.jpg|class=halfwidth|center]]

{{Info|[[File:Info.png]] If Spirit W1 is Powered On for 30 seconds or more in the Bind mode, it will remove previously saved bind data.}}


== Spirit RX7 ==
In order to Bind Spirit RX7 with your Wave radio use supplied Bind plug.

{{Info|[[File:Info.png]] If Spirit RX7 is new (no Bind Data available) a Bind Plug is not required and you can continue with the following section '''Binding with Wave'''.}}


#Insert '''Bind plug''' at the '''BIND port''' and connect Power supply to the Spirit RX7 unit. You can connect BEC or 1-3S Battery at any port.
#Perform binding according following '''Binding with Wave''' section.

[[File:spritrx7-bind.jpg|class=halfwidth|center]]

{{Info|[[File:Info.png]] If Spirit RX7 is Powered On for 30 seconds or more in the Bind mode, it will remove previously saved bind data.}}


== Spirit µRX ==

This micro receiver does require '''NO Bind Plug'''. It is enough to press BIND button at the '''Model/Receiver''' menu and THEN power up receiver.

== Binding with Wave ==

#You can always Bind any Wave receiver by going to the '''Model/Receiver''' menu.
#Press the '''Bind button''' after powering up a receiver with a Bind plug. (Spirit RX7 or Spirit W1)
#After successfull binding you will be notified at the Display. Binding will take no more than 500 ms.
#Bind plug can be removed.

[[File:wave-bind.png|480px|center]]

Stratos 200/en

FuzzyBot — Sun, 02 Aug 2026 09:06:19 GMT

Importing a new version from external source

New page

<languages/>

Spirit units are fully compatible with Stratos 200 and will offer out of the box experience with the latest Spirit 4.0.4 firmware and software.
For the best performance we recommend Spirit 3, Spirit W3, Spirit GT, Spirit GTR or Spirit W1 units. These have full support for '''DShot300 protocol'''.

==Wiring==

You can wire Stratos according following scheme:

*'''CH1''' - S2 Servo
*'''CH2''' - S1 Servo (Left servo)
*'''CH3''' - S3 Servo (Right servo)

*'''PIT''' (Center pin) - Green cable for RPM readings
*'''SAT1''' - ESC Telemetry cable - JST-Servo plug adapter is required. You can find it inside the Stratos box. Signal wire must be connected closer to the main pin headers.

Make sure to dismount Main and Tail blades for a safety reason.

===Spirit 3, Spirit GT===
*'''AUX2''' - Blue cable (Tail Motor)
*'''AUX1''' - ESC cable (Main Motor)

===Spirit W1, Spirit W3, Spirit GTR===
*'''AUX''' - Blue cable (Tail Motor)
*'''THR''' - ESC cable (Main Motor)

==Starting==

#First please install the latest PC software 4.0.4 from our [https://spirit-system.com/download.php Download section].
#Then flash the Firmware '''Spirit Heli 4.0.4''' from the Firmware List.

[[File:StratosFirmware.png|550px]]

===Setup Wizard===

After flashing you can start the '''Setup Wizard''' that include all required settings.
Go through the wizard, select your Receiver type and then select '''STRATOS 200 preset'''. STEP 2 is the most important one.

[[File:StratosWizard.png|550px]]

Once you are at the STEP 5 you need to change channels and it's direction to corespond to the bars you can see.
If you are operating Spirit Wave, everything will be fine out of the box.

=== Wave Radio ===

If using Spirit Wave radio you can directly use the Setup Wizard embedded in the radio. There select micro helicopter and pick the Stratos 200 preset. Go through the Wizard according instructions and from then you are ready to fly.

===Tuning===
'''IMPORTANT''': It is required to adjust '''Swashplate Subtrims''' in the Setup Wizard to obtain levelled swashplate.
This mean to move with CH1, CH2 and CH3 Subtrims in the PC software until all 3 servos are in the center as precise as possible.
Do not move with CH4 subtrim, this is used for configuring minimum RPM for Tail Motor.

After going through the process you are almost Ready to Fly.

==First flight==

#Set Gyro Gain to '''80%''' in your radio.
#Set flat Throttle Curve. Setting 70 - 80% should be equal to 5000 RPM.

== Settings ==

Recommended settings for the current '''4.0.4-r2''' firmware are:

*'''Servos/Rudder - Servo frequency''': 333Hz
*'''Sensor/Cyclic Gain''': 30%
*'''Advanced/Rudder - Pirouette Consistency''': 200
*'''Advanced/Rudder - Revomix''': 4
*'''Advanced/Rudder - Delay''': 30
*'''Advanced/Expert/Rudder - Stop Gain CW''': 100
*'''Advanced/Expert/Rudder - Stop Gain CCW''': 100
*'''Advanced/Expert/Rudder - Stop Smoothing''': 5
*'''Advanced/Expert/Rudder - TTA Gain''': 25
*'''Advanced/Expert/Rudder - TTA Limit''': 15

*'''Advanced/Elevator Filter''': 0
*'''Advanced/Geometry 6°''': 95

*'''Throttle - Pulse''': DShot300
*'''Throttle - Sensing Divider''': 12
*'''Throttle - Gear Ratio''': 1

*'''Governor - Enabled''': Yes
*'''Governor - Response''': 4
*'''Governor - Holding Performance''': 3
*'''Governor - Holding Limit''': 95
*'''Governor - Max. Headspeed''': 6000 RPM

'''For 3D Master mode users:'''
*Sensor/Elevator P Gain: 30
*Sensor/Aileron P Gain: 30
*Sensor/Rudder P Gain: 230
*Sensor/Elevator I Gain: 90
*Sensor/Aileron I Gain: 90
*Sensor/Rudder I Gain: 200
*Sensor/Elevator D Gain: 0
*Sensor/Aileron D Gain: 0
*Sensor/Rudder D Gain: 30

=== Hard 3D Setup ===

For pilots that like to fly hard we recommend to check this page:

[https://forum.spirit-system.com/viewtopic.php?t=6888 STRATOS 200 Setup]

OMP Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 09:05:57 GMT

Importing a new version from external source

Jeti Integration/en

FuzzyBot — Sun, 02 Aug 2026 09:05:55 GMT

Importing a new version from external source

Spirit Wave Voice Output/en

FuzzyBot — Sun, 02 Aug 2026 09:05:48 GMT

Importing a new version from external source

New page

Spirit Wave radios are fully capable of speaking in many languages and can output Voice at various events.

This mean it can be programmed to inform pilot about important data even during flight.

== Supported Language ==
Spirit Wave has Voice support for the following languages:

* English
* Czech
* German
* Italian
* Chinese

Other languages will be added in the following Updates. Alternatively you can Upload your own Voices.

== Voice Generation ==

Voices are of High Quality and are Generated by AI at a remote Servers. This mean that Internet Connection is required for configuring new Voice Output.
Once a Voice is set it is stored at the Wave Radio and will work later at any moment.

== Voice Output Types ==

Spirit Radio can be programmed to have Voice Output for the following:
* Flight Modes
* Timers
* Telemetry Variables
* Device Condition
* Device Events
* Custom Events

All this can be independently set and reconfigured as needed, by default Voice Output is disabled.

=== Flight Modes ===

Voice Output can be configured for each Flight Mode. The output, if enabled, is triggered immediately when Flight Mode is changed and become active.

Go to '''Model - Flight Mode''' page. Then select Flight Mode for which you wish to set Voice Output and press '''Set''' Button.
Lastly go to '''Second page''' that is dedicated to Voice Output.

[[File:wave-voice-output.png|550px]] [[File:wave-voice-output2.png|550px]]

* Bear in mind this settings will not affect other Flight Modes.
* Each Flight Mode can be configured differently.
* Each Flight Mode can have Voice Output enabled or disabled.

'''Text To Speech''' displays text that will be be said. When you can see ''Not Available'' it mean you have to set new Text by pressing at the '''Change''' button.
Then any word or sentence is automatically synthetized and in a blink of eye ready. You can change the Text as needed.

If you need to configure Voice Output for Each Flight mode, it is required to go one page back, select other Flight Mode and set it similarly there.

== Alarms ==

Alarms can set the rest of Voice Output Types. To distinguish Alarm Type well there are two Alarm Groups:

* '''Warnings''' - This Group can contain all Alarms that are triggered when a configured Condition is met.
* '''Reporting''' - This Group can contain all Alarms where a Value has to be Reported at a Periodic Rate.

=== Warnings ===

Warnings are mainly used for Voice Output but can also notify pilot without Voice - you can choose to enable only vibrations.

[[File:wave-voice-warnings.png|550px]]
[[File:wave-voice-warnings2.png|550px]]
[[File:wave-voice-warnings3.png|550px]]
[[File:wave-voice-warnings4.png|550px]]

'''Options:'''
* Condition - Value is Less then ('''<'''), Value is Greater than ('''>'''), Value is Equal to ('''='''), Value is not Equal to ('''not''').
* Value - Alarm Value used for condition checking.
* Vibration - When Alarm is triggered Vibrations are used as Notification.
* Voice - When Alarm is triggered Voice Output is used as Notification.
* Repeat - This will repeat same Alarm (Voice Output and/or Vibration) in case that condition is still met.
* Activation Time - ''During startup'' mean immediately after Radio Bootup or as soon as connection with Model is established.

Certain Alarms can't be set for Value comparison and are behaving only as Event notification. In this case there is '''Event''' displayed instead of Conditions.

=== Reporting ===

[[File:wave-voice-reporting.png|550px]]
[[File:wave-voice-reporting2.png|550px]]
[[File:wave-voice-reporting3.png|550px]]

When Pilot need to hear a Value in a periodic manner it is possible to set Reporting Alarm. Telemetry variables are great example for this.
For example it is possible to Call Out Battery Capacity periodically to find out if it is good time for landing. Or to call out remaining Flight Time based on System Timer.

'''Options:'''
* Repeat - This will repeat Voice Output with a fresh Value based on selected Variable.
* Activation Time - ''During startup'' mean immediately after Radio Bootup or as soon as connection with Model is established. ''Switch'' option can be used for enabling Call Out only when selected Input is in Active position. For example in a certain Switch position you can start to hear current Head Spead periodically. This can be configured to any Switch or Input and any Position as per user requirements.

==== Custom Voices ====

Special type of Reporting Alarm is called '''User'''. This can be set to Call Out any Text based only on configured Wave Radio Input. This is great for programming your Custom Voices with a Special Purpose such as Landing Gear condition, Stabilisation Modes or similar.

Spirit RX/en

FuzzyBot — Sun, 02 Aug 2026 09:05:37 GMT

Importing a new version from external source

New page

<languages />
__NOTOC__
[[File:wavelogo.png|center|128px]]

Spirit RX is name for receiver series designed for Spirit Wave radios. Presently there are following receivers available:
*'''Spirit µRX''' - External micro receiver
*'''Spirit RX7''' - External receiver with 7 outputs
*'''Spirit W1''' - Stabilisation unit with integrated receiver

All receivers have support for Spirit RX bi-directional transmission protocol.
It features support for:
*Transmitting channel data
*Telemetry data
*Integration data - full and strightforward configuration from Wave radio
*Over the Air Update (OTA) - remote and easy update from Wave radio

Everything is done through one, highly optimized BUS.
All Spirit receivers and Spirit units have support for this protocol.

<div style="color:white; background:red; font-size:large; padding: 2px 15px; border-radius:15px; page-break-before: always; font-size: 16pt; ">'''CONTENTS'''</div>
==[[File:spiritrs-mounting.png|22px|sub|]] Mounting ==
*[[Spirit_RX_Mounting|Mounting at the model]]

==[[File:spiritrs-wiring.png|22px|sub|]] Wiring ==
*[[Spirit_RX_Wiring|Wiring with Spirit]]

==[[File:spiritrs-binding.png|22px|sub|]] Binding ==
*[[Spirit_RX_Binding|Binding with Radio]]

==[[File:spiritrs-setup.png|22px|sub|]] Setup ==
*[[Spirit_RX_Setup|Configuring Receiver from Radio]]
*[[Spirit_RX_Updating|Updating Receiver Firmware]]

==[[File:spiritrs-doc.png|22px|sub|]] Certification ==
*[[Spirit_RX_FCC|FCC Declaration of Conformity]]

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 09:05:33 GMT

Importing a new version from external source

OMP Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 09:05:16 GMT

Importing a new version from external source

TelMe Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 09:05:11 GMT

Importing a new version from external source

Spirit Wave Simulator/en

FuzzyBot — Sun, 02 Aug 2026 09:04:47 GMT

Importing a new version from external source

New page

Spirit Wave can be used for controlling almost all commonly used R/C simulators for a training purposes.
There are 3 different options for interfacing Spirit Wave with a Computer or Smart Device.

* Wired: USB-C Cable
* Wireless: WiFi + Wave Studio software
* Wireless: Bluetooth

Alternatively you can use power of Spirit Wave and run our '''Spirit Air''' simulator natively on the radio.

== Wired ==

Wired connection is simple and strightforward solution with the lowest latency. There is no need to make any configuration at Computer side or Wave Radio side.
Use supplied USB-C Cable and plug it in a Free USB port of your Device such as PC, Mac, Smart TV, Smartphone, Tablet.
Immediately after connecting both devices Wave Radio will display '''Gamepad''' Icon. From then your Computer should recognize new USB Device and all is Set Up.

Device is recognized as a System Joystick which mean it can be used with any software that has support for Joystick or Gamepad. This covers the most games and almost all todays R/C simulators.

== WiFi ==

Download and install [[Wave_Studio|Wave Studio]] software first. This option is suitable for all '''Windows'''-based computers or tablets.

Then go to '''Applications - Simulator - Sim Over WiFi''' page and press the '''Launch''' button.

This will create '''Controller (XBOX 360 Gamepad)''' device in Windows.

== Bluetooth ==

To interface Spirit Wave with any BT 4/LE capable Device you can use '''Sim Over BT''' app. From Spirit Wave 1.0.20 firmware you can utilize this feature. It provides great latency for the most pilots.

Go to '''Applications - Simulator - Sim Over BT''' page and press the '''Launch''' button.

Then you will need to do a pairing at your computer or smart device. Scan for a Bluetooth Devices there and then Pair with '''SIM''' Bluetooth Device.
As soon as you will close Sim Over BT app page the Bluetooth connection is turned off.

Supported is:
* PC running Windows, Linux, FreeBSD or other OS with Bluetooth support
* Apple Mac
* Android Devices
* Other BT LE capable Devices

Pairing is required only once. When CONNECTED state is visible System Joystick is created. From then R/C simulator or a game can be launched.

To connect Spirit Wave again to already Paired Device it is enough to only Launch Sim Over BT app again. The most systems should reconnect to Wave automatically. In the most cases it takes only few seconds, with some computers up to 50 seconds.

{{Info|In case that BT Stack was downloaded for the first time, it will require Spirit Wave to repower to make it working.}}

== Spirit Air ==

Spirit Air is R/C model simulator developed by Spirit System. Spirit Wave can run this full featured simulator directly on the radio display without need for any other device or internet connection. You can install it from '''App Store''' easily and for free starting from late December 2025.

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 09:04:43 GMT

Importing a new version from external source

Spirit Wave FlightMode/en

FuzzyBot — Sun, 02 Aug 2026 09:04:33 GMT

Importing a new version from external source

New page

= Flight Modes =
Flight Modes are used for configuring different Model behavior.

Flight Mode can carry different settings such as:
*Throttle Curve
*Collective Pitch Curve
*Dual Rate
*Exponential Curve
*Trims
*Gyro Gain
*Spirit Controller Parameters

All these settings are stored in the Spirit Wave and are immediately applied when particular Flight Mode is active.

[[File:wave-flightmode.png|500px]]

Example of 4 Flight Modes, where Flight Mode called "Normal 2" is active.

== Properties ==
Each Flight Mode has following properties:
*Name
*Input
*Active Position of the Input
*Priority
*Delay
*Voice Output

When a new Model profile is created, only one Flight Mode is available. It is possible to create unlimited amount of new Flight Modes.
All Flight Mode related settings can be found at the '''Model - Flight Mode''' menu.

To easily distinguish Flight Mode you can always see it's name at the left side of the Top system panel. You can configure name of each Flight Mode as needed.

For Flight Mode to be active it is required to set '''Input''' and then set at which Input's position the Flight Mode should be active.
Default Input is '''Switch LU''' at the front left, upper side of the radio. It is common to use 2 or 3-state switch for this purpose.
Position for each Input can be individually configured as needed. If only one Flight Mode is created, there is no need to adjust Input nor Position

You can set same or different Input for more Flight Modes. If Input (Switch) is used for multiple Flight Modes, the radio will determine which Flight Mode is active based on '''Active Position''' only.

If there are conditions during which radio can't determine active Flight Mode, it is determined by a configured '''Priority'''. The lower priority value is, the higher is the priority. Flight Modes are sorted according their Priority in the Flight Mode list. Flight Mode with the highest priority is at the Top of the list.

In certain cases it is required to have Flight Mode activation delayed. Even if all conditions for activation are met the system can remain at a previous Flight mode until configured '''Delay''' period will pass.

'''Voice Output''' can be individually configured for each Flight Mode. See [[Spirit_Wave_Voice_Output|Voice Output]] page.

== Shared Parameters ==

Certain Parameters of the Model can be set as Flight Mode independent or so called '''Global'''. These parameters are following:
*Throttle Curve
*Collective Pitch Curve
*Dual Rate
*Exponential Curve
*Trims
*Gyro Gain

[[File:wave-sharedparams.png|500px]]

Shared Parameters can be set at the second page of the '''Model - Flight Mode''' menu and is independent of active Flight Mode. It is same for each of them.
Each Model profile can have different Shared Parameters.

{{Info|[[File:Info.png]] Example: If pilot knows that Model require same Throttle Curve always but he need more Flight Modes, then it is beneficial to enable Throttle Curve Sharing option.}}
 
By default (for each new model) Dual Rate, Expo, Trims are enabled as Shared Parameters.

Spirit Wave Model/en

FuzzyBot — Sun, 02 Aug 2026 09:04:32 GMT

Importing a new version from external source

New page

=New Model=
__NOTOC__
In order to start with the Wave Radio it is required to create so called '''Model'''. Each model inside the Radio can be bound to specific Receiver.
For this reason it is common to have multiple Models stored inside the Wave Radio for each of your physical R/C model.
In other words, one Model per each R/C model.

Spirit Wave radio has default Model precreated (for Helicopter) when it is launched for the first time or after Factory Defaults.

== Model Creation ==

Press at the Home icon at the bottom panel.

[[File:wave-mainmenu.png|500px]]

Continue with the CREATE button and confirm Dialog with YES.

[[File:wave-model-create.png|500px]]

From then choose appropriate Model Type that correspond to your R/C model.

{{Info|[[File:Info.png]] If it is unlisted type such as a Boat you can use other type - for example Car.}}

[[File:wave-modeltype.png|500px]]

Each Model Type has different Setup Wizard that reflects physical properties of the R/C model, for this reason it is important to select it correctly.

=== Helicopter ===

Spirit Wave radio can be connected with any Flybarless controller.

*If you are using '''Spirit FBL''' unit, choose '''Spirit unit (Heli firmware)''' option.
*For models with no controller (Receiver Only) or for controllers such as MSH Brain, Mikado VBar, BeastX Microbeast, Bavarian Demon Axon or other, select '''Spirit Receiver Only'''.

[[File:wave-model-heli.png|500px]] [[File:wave-model-name.png|500px]]

Continue by using a Swipe gesture to enter Model Name.

=== Plane ===

Spirit Wave radio can be connected with any stabilisation controller.

*If you are using '''Spirit''' unit, choose '''Spirit unit (Aero firmware)''' option.
*For models with no controller (Receiver Only) or for controllers such as Bavarian Demon Cortex select '''Spirit Receiver Only'''.

[[File:wave-model-plane.png|500px]] [[File:wave-model-name.png|500px]]

Continue by using a Swipe gesture to enter Model Name.

== Model Setup ==

Once model is created you can bind it with a receiver according [[Spirit_Wave_Binding|Binding]] section. Then depending on Model Type you can adjust it's parameters.

Main Page/en

FuzzyBot — Sun, 02 Aug 2026 09:04:26 GMT

Importing a new version from external source

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 09:04:25 GMT

Importing a new version from external source

HobbyWingV5 Telemetry/en

FuzzyBot — Sun, 02 Aug 2026 09:04:07 GMT

Importing a new version from external source

Tuning Guide/en

FuzzyBot — Sun, 02 Aug 2026 09:04:06 GMT

Importing a new version from external source

Spirit Wave Battery/en

FuzzyBot — Sun, 02 Aug 2026 09:03:36 GMT

Importing a new version from external source

New page

=Battery=

Spirit Wave Radio is equipped with LiPo battery - '''GensAce 6900 mAh 3.8V'''.


{{Quote|It is prohibited to use battery with a different nominal voltage than 3.8 Volts.}}

{{Quote|Always disconnect battery before changing any radio wiring or changing a components.}}

{{Quote|Do not expose electronics to a high moisture or high temperature.}}

Battery is installed at the tray with a velcro tape. It must be precisely positioned to avoid a contact with a nearby parts, wrong positioning will not allow mounting of the back cover.

Special care must be taken at the battery cables during Radio Chasis closing. Pay extra attention to not touch any electronics part with a conductive tools.

Operator is responsible for careful placement of the cables to avoid damage.

[[File:spirit-radio-battery.jpg|600px]]

== Battery Connection ==

Battery has two leads that must be connected to the Radio with a correct polarity.

{{Quote|Shorting a leads or routes at the PCB could cause fire!}}

[[File:spirit-radio-battery-con.jpg|600px]]

Spirit Wave Updating/en

FuzzyBot — Sun, 02 Aug 2026 09:03:34 GMT

Importing a new version from external source

New page

=Updating Radio=

Spirit Wave can be updated Online directly from the User Interface. This allows very easy method for gaining new features of the Radio and variety of imprevements.

{{Info|[[File:Info.png]] It is always recommended to use the latest firmware, preferably to update all Spirit products to the latest version.}}


== Updater ==

Updater tool is embedded software for doing Firmware Updates easily. No other tool is required for full System update.
The only requirement is working Internet connection.

The Updater tool can be found at the '''Applications''' menu (second Icon from left at the bottom panel).

[[File:wave-app-updater.png|600px]]

Select '''Radio''' and then choose the firmware.

[[File:wave-app-updater2.png|600px]]

Firmware list is automatically displayed as soon as Internet Connection is working. Usually there are more firmwares available, one with the most recent date is the latest one.

[[File:wave-app-updater3.png|600px]]

Immediately after pressing the Update button whole Radio will be updated.

{{Info|[[File:Info.png]] Before updating Spirit Wave it is required to turn off all receivers that are bound to it.}}


=== Updating Process ===
[[File:wave-app-updater4.png|600px]]

#Firmware is downloaded (approximately 50MB).
#Firmware is verified and checked for Integrity.
#Firmware is saved to the memory.
#Radio is restarted automatically after successful updating.

@@ Line 8: / Line 8: @@
 *[[SpiritRS|MANUAL - Spirit RS, Spirit GTR units]]
-*[[SpiritW1|MANUAL - Spirit W1]]
+*[[SpiritW1|MANUAL - Spirit W1, Spirit W3]]
 *[[Spirit_RX|MANUAL - Spirit µRX, RX7]]

← Older revision		Revision as of 10:29, 2 August 2026
Line 6:		Line 6:
	[[File:Logo.png\|class=halfwidth\|center]]		[[File:Logo.png\|class=halfwidth\|center]]

−	<div align=center>Version 4.0.0</div>	+	<div align=center>Version 4.0.2</div>

@@ Line 4: / Line 4: @@
 ==[[File:Manual.png|22px|sub|]] Online Manual ==
-*[[Manual|MANUAL - μSpirit, Spirit, Spirit Pro, Spirit 2, Spirit GT units]]
+*[[Manual|MANUAL - μSpirit, Spirit, Spirit Pro, Spirit 2, Spirit 3, Spirit GT units]]
 *[[SpiritRS|MANUAL - Spirit RS, Spirit GTR units]]

@@ Line 10: / Line 10: @@
 * '''Battery''': 6900mAh 3.8V Premium Grade LiPo
 * '''Current Consumption''': 850 mA max., 45 nA Standby
-* '''RF Power''': 380mW max.
+* '''RF Power''': 380mW max. (depending on Country)
 * '''WiFi''': 2.4/5 GHz b/g/n/a/ac
 * '''Bluetooth''': BT/BTLE 5

@@ Line 14: / Line 14: @@
 == Telemetry Cable ==
-To allow the telemetry data transmission '''Telem CC cable''' is required. This cable is available in our [http://store.spirit-system.com/en/accessories/36-telemcc-cable.html Eshop].
+To allow the telemetry data transmission '''Telem CC cable''' is required. This cable is available in our [https://store.spirit-system.com/en/accessories/36-telemcc-cable.html Eshop].
 [[File:telemcc.png|280px]]

@@ Line 29: / Line 29: @@
 :::*There is a mechanical issue. Check by spooling up the motor with no blades, then move with the tail push rod carefully by hand from end to end. (push rod disconnected from servo).
 :::*Tail servo is too slow (0.07s/60° or higher) - increase the '''Advanced/Rudder Revomix''' to value 1-4. Higher values are not recommended.
-:'''6.''' When above steps are done, you can tune the Stopping Behavior. For this purpose use the '''Advanced/Rudder Stop''' parameters. Value determine how aggressive the Rudder Stopping and Steering is. If you like sharp stops, you should set value between 6 to 8. If you like extra sharp behavior, then value higher than 10 are good for you. High value will add extra stress for servos and mechanics, so you should be carefull. If you like smooth stopping so that steering is also very smooth, you should set values between 5-7. If value is too low, the rudder reaction could feel delayed. In case the tail stopping is not equal or overshooting to one side, you can decrease the Rudder Stop - A or Stop - B. Stop - A will affect stopping from Clock-Wise turn, while Stop - B will affect stopping from Counter Clock-Wise turn. Stop - A is usually smaller by 1 - 2 points from Stop - B.
+:'''6.''' (OPTIONAL) When above steps are done, you can tune how sharp tail will behave. For this purpose use the '''Advanced/Rudder Feed Forward''' parameter. Value determine how aggressive the Rudder steering is. If you like quick reaction, you should set value between 6 to 8. If you like extra sharp behavior, then value higher than 10 are good for you. High value will add extra stress for servos and mechanics, so you should be carefull.
 :'''7.'''  (OPTIONAL) Once you are satisfied with Tail performance and steering, the last step is to tune Stopping behavior. Use parameters located at the '''Advanced/Expert/Rudder/Stop Gain'''. There you can tune Stop Gain for Clock Wise (CW) and Counter Clock Wise (CCW) direction. Increase the value if you need more agressive stopping. Decrease if you want smoother stopping. If you want agressive stopping but there is a bounce back visible, you can reduce it by increasing '''Rudder - Stop Smoothing''' value. In that way you can reach the best performance without a compromise.

@@ Line 11: / Line 11: @@
 * Jeti Duplex receiver with a free EX port.
 * Jeti Integration cable available in our stores (not for Spirit 3, GT).
-* [https://spirit-system.com/download.php Configuration file] for the transmitter - Click at the JETI icon at the linked page.
+* [https://spirit-system.com/download.php Integration BIN file] for the transmitter - Click at the JETI icon at the linked page.
 == Wiring ==
@@ Line 58: / Line 58: @@
 == Transmitter preparation ==
-Now download  [https://spirit-system.com/download.php Configuration file] from our Spirit web page by clicking at the JETI icon at the bottom of the web page, which has ZIP extension. The file archive must be extracted first (by Right click). You will obtain SPIRIT-3-3 folder.
+Now download  [https://spirit-system.com/download.php Configuration file] from our Spirit web page by clicking at the JETI icon at the bottom of the web page, which has ZIP extension. The file archive must be extracted first (by Right click). You will obtain SPIRIT-3-X folder.
 Content of this folder must be copied to the '''Devices''' directory at the SD-Card of your transmitter.
 Without this you will see an error message when the Spirit device is opened.

@@ Line 13: / Line 13: @@
 == Interfacing ==
-Connect the Telemetry cable to the primary Spektrum satellite port ('''SAT1''') in the unit - apply for Spirit 2, Spirit RS, Spirit Pro, Spirit GT, Spirit GTR.
+Connect the Telemetry cable to the primary Spektrum satellite port ('''SAT1''') in the unit - apply for Spirit 2, Spirit RS, Spirit Pro, Spirit GT, Spirit GTR, Spirit W1.
 There is no support for Spirit v1 units.

@@ Line 29: / Line 29: @@
 === Spirit 3, Spirit GT ===
-Spirit GT require only stright cable supplied with the unit itself. Cable must be connected at the RUD port with no modification.
+Spirit 3 and Spirit GT require only stright cable supplied with the unit itself. Cable must be connected at the RUD port with no modification.
 [[File:Jeti-wiring-gt.jpg|550px]]

@@ Line 25: / Line 25: @@
 [[File:unit-telemuomp.jpg|350px]]
-Servo connector of the Telem OMP cable should be connected to the ESC - programming port. Make sure to connect Orange wire of the Telem OMP cable at the TX pin. Brown pin at the '''-''' pin.
+Servo connector of the Telem OMP cable should be connected to the ESC - programming port. Make sure to connect Orange wire of the Telem OMP cable at the '''TX pin'''. Brown pin at the '''-''' pin.
 '''XDFly ESC Integration with Wave''' require to use '''RX pin''' of the ESC.

@@ Line 8: / Line 8: @@
 == ESC configuration ==
-With usage of the Castle Link interface, please start the [http://www.castlecreations.com/downloads Castle Link software] to open the configuration settings of your ESC.
+With usage of the Castle Link interface, please start the [https://www.castlecreations.com/downloads Castle Link software] to open the configuration settings of your ESC.
 There you have to enable Link-Live feature.

@@ Line 34: / Line 34: @@
 | style="width: 33%;"|  [[Spirit_Wave|&larr; Main Page]]
 | style="width: 33%;text-align:center;"| [[#up|&uarr;Up&uarr;]]
-| style="text-align:right;" | [[Spirit_Wave_Intro|Radio Preparation &rarr;]]
+| style="text-align:right;" | [[Spirit_Wave_Preparation|Radio Preparation &rarr;]]
 |}
 ----
 </div>

@@ Line 41: / Line 41: @@
 ===Tuning Procedure===
 :'''1.''' Increase the '''Sensor/Cyclic Gain''' if you can observe the cyclic is not level during pitch pumps or flight is not precise. Mostly values around 60% are optimal for all models. You shouldn't set the gain as high as possible always. If gain is too high, you could observe Aileron oscillations, especially when descending slowly or while doing Tic-Toc maneuver. Sometimes it is caused by too soft head dampeners or non-flybarless blades as well. But if you can achieve values higher than 50% then it is optimal.
-:'''2.''' Set the '''Sensor/Rotation Rate''' parameter to the extent that flips and rolls are fast enough. Be carefull to not set it higher than your mechanics can handle. The highest value for the most models is between 11 - 13. If the value is too high, steering is not precise and sometimes you can observe that rate is not constant (Once you finish the cyclic input it will continue for a fraction of second).
+:'''2.''' Set the '''Sensor/Rotation Rate''' parameter to achieve required Flip and Roll Rate. Be carefull to not set it higher than your mechanics can handle. From certain point the model will stop increasing the rate. This mean your Cyclic Ring or Head Speed could be too low. Maximum Flip/Roll Rate for the most models is roughly 360°/s. If the value is too high, steering will initially react very quickly, but then it will slow down.
-:'''3.''' If input reactions are delayed, you want likely to increase the '''Advanced/Cyclic Feed Forward''' which plays very important role in overall behavior. If you are switching from e.g. Microbeast, you will be comfortable with values between 4 - 6. If you are switching from V-Bar you will like 6 - 8. If you are switching from Bavarian Demon, you will love values of 8 - 10. The higher values are more demanding for the servos. In bigger helicopter you can even risk Boom Strike with too high values. Too high value will induce too sharp movements and also elevator bounce-back. Too low value will cause very delayed (smooth) steering.
+:'''3.''' If input reactions are delayed, you want likely to increase the '''Advanced/Cyclic Feed Forward''' which plays very important role in overall behavior. Generally value 4 is fine for the most pilots. Too high value will induce unwanted effect of Elevator Bounce-Back. Low value will behave delayed and too smooth.
 :'''4.''' Now it is time to set the '''General/Flight Style'''. This is the last parameter that determines flight characteristics. If you like very linear movements from the stick center to full stick deflection then you will like low values. If you like flybar behavior, so that feeling around center is smooth but with faster input you will get a sharp response, then you want to set high value. With various combinations of Flight Style and Cyclic Feed Forward you can change Cyclic feeling noticeable. If you are switching from e.g. Microbeast, you will be comfortable with values between 4 - 6. If you are switching from V-Bar you will like 6 - 8. Difference between settings can be seen especially in a pirouette maneuvers and also Tic-Tocs. If value is too high, then blade' efficiency can decrease and motor can be overloaded. With higher value a sharp movements are transferred faster to the servos. Also if you are doing aggressive maneuvers, it will stop faster when stick is returned to the center. If the value is too low, then a Tic-Tocs can't be done fast enough, Piroflips can't be done precisely, etc. For beginners we recommend to leave default value. This parameter is only about your preference and both low and high value has its positive and negative side. For example, if you want smooth feeling around center with natural characteristics, you can set value of 8 for the Flight Style and Cyclic Feed Forward to 6 - 10.
 :'''5.''' Lastly, you might need to eliminate Elevator Bounce-Back effect. This can occur with high Cyclic Feed Forward. To reduce this effect increase '''Advanced/Elevator Filter''' parameter. Value between 2 - 3 should be fine for almost all helicopters. When using an aggressive blades you will need value of 4. Especially for bigger size helicopter, the value can be higher. In case of too high value, elevator movement can be too smooth and in some cases elevator can oscillate with low RPM during hovering. Set it only as high as really necessary.

@@ Line 1: / Line 1: @@
 <languages />
-OMP M4 ESC has telemetry feature built-in in the Programming port. This allows telemetry data transmission to the unit.
+This guide fits '''OMP''' and '''ZTW''' ESCs. OMP and ZTW and ESC has telemetry feature built-in in the Programming port. This allows telemetry data transmission to the unit.
 Similarly XDFly ESCs have telemetry feature built-in. Additionally they support ESC Integration with Spirit Wave radios. Wiring is slightly different!

@@ Line 20: / Line 20: @@
 :If the values for Rudder End-Points in the Limits Tab are less than 70, then it is too low. That mean that servo precision vs mechanical gain is not optimal. You can fix the issue by putting ball link closer to the center at the rudder servo arm so that limit can become higher. In case the value is more than 170 there is mostly too high servo precision vs mechanical gain. You should put longer servo arm, so the ball linkage can be further away from the center. Make sure you have configured limits so that tail slider is moving from end to end, but without any mechanical binding (servo buzzing). In case your tail mechanics allows a pitch higher than 45°, do not set limits that high. It is not required that limits for both sides are equal.
-===Tuning Procedure:===
+===Tuning Procedure===
 :'''1.''' Set '''Sensor/Rotation Rate''' for the Rudder - this parameter determine how fast the rudder will rotate around its axis. Values between 300 - 500°/s are used by the most pilots. Default value of 300 is fine for beginners and advanced pilots. 500°/s is fine for experienced 3D pilot.
 :'''2.''' Set '''Advanced/Rudder Delay''' accordingly for your servo type - please see the [[Servo list]] where you can find optimal range. For ''Futaba BLS'' servos and ultra fast servos it is fine to set 0. Slower the servo is, the higher value should be configured. If you are not sure, leave this parameter (value of 2 should fit for average digital servos).

@@ Line 8: / Line 8: @@
 == Telemetry Cable ==
-To allow the telemetry data transmission the '''Telem OMP cable''' is required. This cable is available in our [http://store.spirit-system.com/en/accessories/34-telemuni-cable.html Eshop].
+To allow the telemetry data transmission the '''Telem OMP cable''' is required. This cable is available in our [https://store.spirit-system.com/en/accessories/65-telemomp-cable.html Eshop].
 Telem UNI cable can be used too after small modification using a needle.

@@ Line 5: / Line 5: @@
 == Telemetry Cable ==
-To allow the telemetry data transmission the '''Telem KONTRONIK v2 cable''' is required. This cable is available in our [http://store.spirit-system.com/en/accessories/47-telemkontronikv2-cable.html Eshop].
+To allow the telemetry data transmission the '''Telem KONTRONIK v2 cable''' is required. This cable is available in our [https://store.spirit-system.com/en/accessories/47-telemkontronikv2-cable.html Eshop].
 [[File:telemkontronikv2.png|280px]]

@@ Line 18: / Line 18: @@
 '''Prerequisite step -''' You can verify that the Rudder servo End-points are not too low or either not too high.}}
 <p></p>
-:If the values for Rudder End-Points in the Limits Tab are less than 70, then it is too low. That mean that servo precision vs mechanical gain is not optimal. You can fix the issue with putting ball link closer to the center at the rudder servo so that limit can be higher. In case the value is more than 170 there is mostly too high servo precision vs mechanical gain. You should put longer servo arm, so the ball linkage can be further. Be sure you have configured limits so that tail slider is moving from end to end, but without any mechanical binding (servo buzzing). In case your tail mechanics allows a pitch higher than 45°, do not set limits that high. It is not absolutely necessary that limits for both sides are equal.
+:If the values for Rudder End-Points in the Limits Tab are less than 70, then it is too low. That mean that servo precision vs mechanical gain is not optimal. You can fix the issue by putting ball link closer to the center at the rudder servo arm so that limit can become higher. In case the value is more than 170 there is mostly too high servo precision vs mechanical gain. You should put longer servo arm, so the ball linkage can be further away from the center. Make sure you have configured limits so that tail slider is moving from end to end, but without any mechanical binding (servo buzzing). In case your tail mechanics allows a pitch higher than 45°, do not set limits that high. It is not required that limits for both sides are equal.
 ===Tuning Procedure:===

@@ Line 4: / Line 4: @@
 == Telemetry Cable ==
-To allow the telemetry data transmission the '''Telem UNI cable''' is required. This cable is available in our [http://store.spirit-system.com/en/accessories/34-telemuni-cable.html Eshop].
+To allow the telemetry data transmission the '''Telem UNI cable''' is required. This cable is available in our [https://store.spirit-system.com/en/esc-telemetry/34-telemuni-cable.html Eshop].
 [[File:telemuni.png|280px]]

@@ Line 10: / Line 10: @@
 <p></p>
-First from all, you should try a default settings that are recommended. There are basic parameters that you have to set at the beginning (for example in the Setup wizard) but other are useful to adjust feeling and flight characteristics. Basically, you can set the behavior so that it is very similar to any known flybarless or flybared system.
+First from all, you should try a default settings that are recommended. There are basic parameters that you have to set at the beginning (for example at the Setup Wizard) but other are useful to adjust feeling and flight characteristics. Basically, you can set the behavior so that it is very similar to any known flybarless or flybared system.
-If you are in condition that the helicopter is flying, but you need to do some corrections, you should start with the rudder settings first.
+If you are in condition that the helicopter is flying, but you need to do some tweaking, you should start with the Rudder settings first. This is because poor Tail performance will lead to unwanted effects of the swashplate.
 == RUDDER TUNING ==
@@ Line 21: / Line 21: @@
 ===Tuning Procedure:===
-:'''1.''' Set '''Sensor/Rotation Rate''' for the rudder - this parameter determine how fast the rudder will rotate around its axis. Values between 8-11 are used by allmost all pilots. Default value of 8 is fine for beginners. While value of 11 is good for 3D maneuvers where faster pirouettes are needed.
+:'''1.''' Set '''Sensor/Rotation Rate''' for the Rudder - this parameter determine how fast the rudder will rotate around its axis. Values between 300 - 500°/s are used by the most pilots. Default value of 300 is fine for beginners and advanced pilots. 500°/s is fine for experienced 3D pilot.
-:'''2.''' Set '''Advanced/Rudder Delay''' accordingly for your servo type - please see the [[Servo list]] where you can find optimal range. For ''Futaba BLS'' servos and ultra fast servos it is fine to set 0. Slower the servo is, the higher value should be configured. If you are not sure, leave this parameter (value of 5 should fit for average digital servos).
+:'''2.''' Set '''Advanced/Rudder Delay''' accordingly for your servo type - please see the [[Servo list]] where you can find optimal range. For ''Futaba BLS'' servos and ultra fast servos it is fine to set 0. Slower the servo is, the higher value should be configured. If you are not sure, leave this parameter (value of 2 should fit for average digital servos).
 :'''3.''' Set '''Gyro Gain''' (usually in your transmitter) to the value, that tail is holding well, but not oscillating in any maneuver (for example Pitch pumping). This value should be as high as possible always. If you are observing tail oscillation, you should decrease the gain to eliminate it. Please note that it is recommended to change the Gain only in this step. In case that you have achieved 100% Gyro Gain with no oscillation, please increase '''Sensor/Rudder Common Gain''' which will multiply the Gyro Gain.
 :'''4.''' Now, when your gain is configured, your tail can still not hold the position exactly. That's because your mechanical gain is not high as necessary. You can fix it by increasing '''Advanced/Piro Consistency''' value. Increase it by 5 gradually until the tail will hold. The value should be nearly in all cases between 165 - 200. With higher values the rudder will rotate more constantly and will become sharper. With bigger size helicopter the value is always higher. It depends mostly on the helicopter construction (manufacturer), servo arm and servo type. For ''Futaba BLS'' servos or similar, it is needed to increase the value even more (in rare cases to value of 220). You shouldn't set the parameter too high if not necessary (always set only as high as really necessary), otherwise ''tail oscillation'' in high extent can occur. You can verify it in a ''Fast Forward Flight'' or ''Pitch Pumps'' whether the value is too high and you can see any oscillations.