Help
Translate
Jump to:
navigation
,
search
Settings
Group
Recent translations
Recent additions
Sandbox messages
Align HE50H22 RPM Sensor
Avian Telemetry
Bluetooth Module
Castle Telemetry
CC Phoenix Edge RPM output
Coaxial
Configuration
ESC telemetry
First flight
Flashing Failed
FrSky FBus
FrSky FBUS
FrSky FPort
Futaba
Futaba Telemetry
GeoLink
GeoLink Altidude Limit
GeoLink Altitude Hold
GeoLink Altitude Limit
GeoLink Auto Landing
GeoLink Configuration
GeoLink Features
GeoLink Geofence
GeoLink Introduction
GeoLink Logging
GeoLink Mounting
GeoLink Position Hold
GeoLink Return to Home
GeoLink Troubleshooting
Governor
Graupner SUMD
HobbyWing Platinum ESC v3/v4 RPM output
HobbyWing Telemetry
HobbyWingV5 Telemetry
Hott Integration
HoTT Telemetry
Hyperion RPM Sensor
Imprecise Rescue
Installation
Introduction
Jeti Integration
Jive Telemetry
Kontronik Telemetry
Main Page
Manual
Normal Mode
OMP Telemetry
OpenTX 2.2
OpenTX Integration
PDF Download
Problems and Solutions
Rescue (Acro)
Rescue (Automatic)
Rescue (Normal)
S-BUS Adapter
Safety
Scorpion Telemetry
Servo list
Spektrum
Spektrum Integration
Spektrum PWM connection
Spektrum SRXL2
Spirit RPM Sensor
Spirit RX Updating
Spirit Settings under Mac
Spirit Settings under Windows
Spirit Wave
Spirit Wave Battery
Spirit Wave FlightMode
Spirit Wave Intro
Spirit Wave Model
Spirit Wave Opening
Spirit Wave Safety
Spirit Wave Simulator
Spirit Wave Specs
Spirit Wave UI
Spirit Wave Updating
SpiritRS
SpiritRS Binding
SpiritRS Computer
SpiritRS FCC
SpiritRS Mounting
SpiritRS Preparation
SpiritRS Safety
SpiritRS Setup
SpiritRS Telemetry
SpiritRS Wiring
SpiritW1
SPM4649T
Stabi mode
Stabilization (Acro)
Stabilization (Normal)
Stabilization (Scale)
TelMe Telemetry
Thanks
Tuning Guide
Unequal Collective Pitch
Wifi-Link
Wiring
YGE ESC RPM output
YGE Telemetry
Language
aa - Afar
ab - Abkhazian
ace - Achinese
ady - Adyghe
ady-cyrl - адыгабзэ
aeb - Tunisian Arabic
aeb-arab - تونسي
aeb-latn - Tûnsî
af - Afrikaans
ak - Akan
aln - Gheg Albanian
am - Amharic
an - Aragonese
ang - Old English
anp - Angika
ar - Arabic
arc - Aramaic
arn - Mapuche
arq - Algerian Arabic
ary - Moroccan Arabic
arz - Egyptian Arabic
as - Assamese
ase - American Sign Language
ast - Asturian
av - Avaric
avk - Kotava
awa - Awadhi
ay - Aymara
az - Azerbaijani
azb - تۆرکجه
ba - Bashkir
bar - Bavarian
bbc - Batak Toba
bbc-latn - Batak Toba
bcc - Southern Balochi
bcl - Bikol Central
be - Belarusian
be-tarask - Belarusian (Taraškievica orthography)
bg - Bulgarian
bgn - Western Balochi
bho - Bhojpuri
bi - Bislama
bjn - Banjar
bm - Bambara
bn - Bengali
bo - Tibetan
bpy - Bishnupriya
bqi - Bakhtiari
br - Breton
brh - Brahui
bs - Bosnian
bto - Iriga Bicolano
bug - Buginese
bxr - буряад
ca - Catalan
cbk-zam - Chavacano de Zamboanga
cdo - Min Dong Chinese
ce - Chechen
ceb - Cebuano
ch - Chamorro
cho - Choctaw
chr - Cherokee
chy - Cheyenne
ckb - Central Kurdish
co - Corsican
cps - Capiznon
cr - Cree
crh - Crimean Turkish
crh-cyrl - Crimean Turkish (Cyrillic script)
crh-latn - Crimean Turkish (Latin script)
cs - Czech
csb - Kashubian
cu - Church Slavic
cv - Chuvash
cy - Welsh
da - Danish
de - German
de-at - Austrian German
de-ch - Swiss High German
de-formal - German (formal address)
diq - Zazaki
dsb - Lower Sorbian
dtp - Central Dusun
dty - डोटेली
dv - Divehi
dz - Dzongkha
ee - Ewe
egl - Emilian
el - Greek
eml - Emiliano-Romagnolo
en - English
en-ca - Canadian English
en-gb - British English
eo - Esperanto
es - Spanish
et - Estonian
eu - Basque
ext - Extremaduran
fa - Persian
ff - Fulah
fi - Finnish
fit - Tornedalen Finnish
fj - Fijian
fo - Faroese
fr - French
frc - Cajun French
frp - Arpitan
frr - Northern Frisian
fur - Friulian
fy - Western Frisian
ga - Irish
gag - Gagauz
gan - Gan Chinese
gan-hans - Simplified Gan script
gan-hant - Traditional Gan script
gd - Scottish Gaelic
gl - Galician
glk - Gilaki
gn - Guarani
gom - Goan Konkani
gom-deva - Goan Konkani (Devanagari script)
gom-latn - Goan Konkani (Latin script)
got - Gothic
grc - Ancient Greek
gsw - Swiss German
gu - Gujarati
gv - Manx
ha - Hausa
hak - Hakka Chinese
haw - Hawaiian
he - Hebrew
hi - Hindi
hif - Fiji Hindi
hif-latn - Fiji Hindi (Latin script)
hil - Hiligaynon
ho - Hiri Motu
hr - Croatian
hrx - Hunsrik
hsb - Upper Sorbian
ht - Haitian Creole
hu - Hungarian
hy - Armenian
hz - Herero
ia - Interlingua
id - Indonesian
ie - Interlingue
ig - Igbo
ii - Sichuan Yi
ik - Inupiaq
ike-cans - Eastern Canadian (Aboriginal syllabics)
ike-latn - Eastern Canadian (Latin script)
ilo - Iloko
inh - Ingush
io - Ido
is - Icelandic
it - Italian
iu - Inuktitut
ja - Japanese
jam - Jamaican Creole English
jbo - Lojban
jut - Jutish
jv - Javanese
ka - Georgian
kaa - Kara-Kalpak
kab - Kabyle
kbd - Kabardian
kbd-cyrl - Адыгэбзэ
kg - Kongo
khw - Khowar
ki - Kikuyu
kiu - Kirmanjki
kj - Kuanyama
kk - Kazakh
kk-arab - Kazakh (Arabic script)
kk-cn - Kazakh (China)
kk-cyrl - Kazakh (Cyrillic script)
kk-kz - Kazakh (Kazakhstan)
kk-latn - Kazakh (Latin script)
kk-tr - Kazakh (Turkey)
kl - Kalaallisut
km - Khmer
kn - Kannada
ko - Korean
ko-kp - 한국어 (조선)
koi - Komi-Permyak
kr - Kanuri
krc - Karachay-Balkar
kri - Krio
krj - Kinaray-a
ks - Kashmiri
ks-arab - Kashmiri (Arabic script)
ks-deva - Kashmiri (Devanagari script)
ksh - Colognian
ku - Kurdish
ku-arab - كوردي (عەرەبی)
ku-latn - Kurdish (Latin script)
kv - Komi
kw - Cornish
ky - Kyrgyz
la - Latin
lad - Ladino
lb - Luxembourgish
lbe - лакку
lez - Lezghian
lfn - Lingua Franca Nova
lg - Ganda
li - Limburgish
lij - Ligurian
liv - Livonian
lmo - Lombard
ln - Lingala
lo - Lao
loz - Lozi
lrc - Northern Luri
lt - Lithuanian
ltg - Latgalian
lus - Mizo
luz - Southern Luri
lv - Latvian
lzh - Literary Chinese
lzz - Laz
mai - Maithili
map-bms - Basa Banyumasan
mdf - Moksha
mg - Malagasy
mh - Marshallese
mhr - Eastern Mari
mi - Maori
min - Minangkabau
mk - Macedonian
ml - Malayalam
mn - Mongolian
mo - молдовеняскэ
mr - Marathi
mrj - Western Mari
ms - Malay
mt - Maltese
mus - Creek
mwl - Mirandese
my - Burmese
myv - Erzya
mzn - Mazanderani
na - Nauru
nah - Nāhuatl
nan - Min Nan Chinese
nap - Neapolitan
nb - Norwegian Bokmål
nds - Low German
nds-nl - Low Saxon
ne - Nepali
new - Newari
ng - Ndonga
niu - Niuean
nl - Dutch
nl-informal - Nederlands (informeel)
nn - Norwegian Nynorsk
nov - Novial
nrm - Nouormand
nso - Northern Sotho
nv - Navajo
ny - Nyanja
oc - Occitan
olo - Livvi-Karelian
om - Oromo
or - Oriya
os - Ossetic
pa - Punjabi
pag - Pangasinan
pam - Pampanga
pap - Papiamento
pcd - Picard
pdc - Pennsylvania German
pdt - Plautdietsch
pfl - Palatine German
pi - Pali
pih - Norfuk / Pitkern
pl - Polish
pms - Piedmontese
pnb - Western Punjabi
pnt - Pontic
prg - Prussian
ps - Pashto
pt - Portuguese
pt-br - Brazilian Portuguese
qqq - Message documentation
qu - Quechua
qug - Chimborazo Highland Quichua
rgn - Romagnol
rif - Riffian
rm - Romansh
rmy - Romani
rn - Rundi
ro - Romanian
roa-tara - tarandíne
ru - Russian
rue - Rusyn
rup - Aromanian
ruq - Megleno-Romanian
ruq-cyrl - Megleno-Romanian (Cyrillic script)
ruq-latn - Megleno-Romanian (Latin script)
rw - Kinyarwanda
sa - Sanskrit
sah - Sakha
sat - Santali
sc - Sardinian
scn - Sicilian
sco - Scots
sd - Sindhi
sdc - Sassarese Sardinian
sdh - Southern Kurdish
se - Northern Sami
sei - Seri
ses - Koyraboro Senni
sg - Sango
sgs - Samogitian
sh - Serbo-Croatian
shi - Tachelhit
shi-latn - Tašlḥiyt
shi-tfng - ⵜⴰⵛⵍⵃⵉⵜ
si - Sinhala
sk - Slovak
sl - Slovenian
sli - Lower Silesian
sm - Samoan
sma - Southern Sami
sn - Shona
so - Somali
sq - Albanian
sr - Serbian
sr-ec - Serbian (Cyrillic script)
sr-el - Serbian (Latin script)
srn - Sranan Tongo
ss - Swati
st - Southern Sotho
stq - Saterland Frisian
su - Sundanese
sv - Swedish
sw - Swahili
szl - Silesian
ta - Tamil
tcy - Tulu
te - Telugu
tet - Tetum
tg - Tajik
tg-cyrl - Tajik (Cyrillic script)
tg-latn - Tajik (Latin script)
th - Thai
ti - Tigrinya
tk - Turkmen
tl - Tagalog
tly - Talysh
tn - Tswana
to - Tongan
tokipona - Toki Pona
tpi - Tok Pisin
tr - Turkish
tru - Turoyo
ts - Tsonga
tt - Tatar
tt-cyrl - Tatar (Cyrillic script)
tt-latn - Tatar (Latin script)
tum - Tumbuka
tw - Twi
ty - Tahitian
tyv - Tuvinian
tzm - Central Atlas Tamazight
udm - Udmurt
ug - Uyghur
ug-arab - Uyghur (Arabic script)
ug-latn - Uyghur (Latin script)
uk - Ukrainian
ur - Urdu
uz - Uzbek
uz-cyrl - ўзбекча
uz-latn - oʻzbekcha
ve - Venda
vec - Venetian
vep - Veps
vi - Vietnamese
vls - West Flemish
vmf - Main-Franconian
vo - Volapük
vot - Votic
vro - Võro
wa - Walloon
war - Waray
wo - Wolof
wuu - Wu Chinese
xal - Kalmyk
xh - Xhosa
xmf - Mingrelian
yi - Yiddish
yo - Yoruba
yue - Cantonese
za - Zhuang
zea - Zeelandic
zh - Chinese
zh-cn - Chinese (China)
zh-hans - Simplified Chinese
zh-hant - Traditional Chinese
zh-hk - Chinese (Hong Kong)
zh-mo - 中文(澳門)
zh-my - 中文(马来西亚)
zh-sg - Chinese (Singapore)
zh-tw - Chinese (Taiwan)
zu - Zulu
Export for off-line translation
Export in native format
{{DISPLAYTITLE:Wiring}}<languages /> <div id="up"></div> Spirit can be used as a standalone tail gyro or as a flybarless system or as a flybar stabilisation unit. == STANDALONE GYRO AND FLYBAR == Owners of flybarred helicopters can take advantage of the heading hold gyro, which keeps the tail in the direction given by the transmitter regardless of effects from wind or any outside forces. Connect the rudder servo to the ''CH4'' port of the Spirit unit. If you also use a standard receiver, you will need to connect GEAR (or AUX) from your receiver to the AUX port on the Spirit unit. Also, you will need to connect your receiver RUD port to the RUD port on the Spirit unit. Even if you do have a flybarred model, you can also connect the unit in the same way as a you would a flybarless one. This allows you to use the full potential of the unit including Stabilization and Rescue mode. In order for this to work correctly, it is necessary to enable the ''Flybar mechanic'' parameter in the Advanced/Expert window during setup. All other parameters can be configured just the same as with a flybarless head. == FLYBARLESS == Flybarless helicopters can take advantage of the full capabilities of the Spirit unit. The Spirit will stabilize the model on all axes and also make it less affected by wind, extend flight times and increase the agility of your model. When properly set up, flight characteristics should be more stable which will give you the confidence to carry out even the most challenging maneuvers. Flybarless rotor blades are also different from blades designed for flybarred models. For optimum flight characteristics it is recommended to use them. When using the Spirit unit as a flybarless system, all servos should be connected in the corresponding positions: == CONNECTOR ORIENTATION == Before plugging-in any connector to the Spirit unit please check carefully following instructions. See how to connect all cables in the right orientation with respect to Spirit unit you have. === μSpirit === {{Quote|Pin layout of the '''JST-ZH(R) connectors is different''' from standard Servo connectors. BROWN (Middle) wire is GND pin. ORANGE wire is SIGNAL pin. RED wire is +5V (BEC voltage). By using '''JST-Servo''' cables you can connect a classic Servos and all Spirit peripherals to the μSpirit even with Servo connectors.}} [[File:uspirit-polarity.png|280px|center]] === Spirit and Spirit Pro === All cables connected to the unit must be oriented so that the signal wire (ORANGE wire) is closer to the connector pin label, towards the center of the unit. This orients the negative (BROWN wire) toward the edge of the unit. [[File:spiritpro-polarity.png|300px|center]] === Spirit 2, Spirit RS, Spirit GT, Spirit GTR === All cables connected to the unit must be oriented so that the signal wire (ORANGE wire) is at the top of the unit. This orients the negative (BROWN wire) at the bottom of the unit. == SERVOS WIRING == Spirit units have full support for all types of servos. Please proceed according the Setup Wizard in Spirit Settings software to see how to connect the servos properly. <p></p> {{Quote|'''Spirit is pre-programmed to 1520µs servo neutral impulse and 50Hz frequency – please ensure you have the correct servo parameters selected as specified by your servo manufacturer. <br/> '''If the neutral impulse of your servo/s is different to the above, such as 760µs, do not connect this servo yet as it could be damaged.''' }} Some connectors have non-standard dimensions that could interfere with neighboring connectors after plugging in the unit. As a solution, we recommend replacing these connectors with JR or Futaba type. '''Never plug a connector for powering the unit into the SYS or ELE/PIT/AIL positions or you may risk damaging the unit.''' <p></p> {| style="width:75%;" |<span style="color:red">'''μSpirit'''</span> |- |''CH1'' – Pitch / Aileron servo |- |''CH2'' – Elevator servo |- |''CH3'' – Aileron / Pitch servo |- |''CH4'' – Rudder servo / Rudder ESC |} <p></p> {| style="width:75%;" |<span style="color:red">'''Spirit, Spirit 2, Spirit RS'''</span> |- |''CH1'' – Pitch / Aileron servo |- |''CH2'' – Elevator servo |- |''CH3'' – Aileron / Pitch servo |- |''CH4'' – Rudder servo |} <p></p> {| style="width:75%;" |<span style="color:red">'''Spirit Pro, Spirit GT, Spirit GTR'''</span> |- |''CH1'' – Pitch / Aileron servo |- |''CH2'' – Elevator servo |- |''CH3'' – Aileron / Pitch servo |- |''CH4'' – Rudder servo |- | |- | |- |''CH0'' – auxiliary (optional) cyclic servo for CCPM 90 swashplate type. |} {{Info|[[File:info.png]] Servos at positions CH1 and CH3 are dependent on the Swashplate settings. Aileron servo on the model is mostly positioned on the right side while pitch on the left side. }} == ESC/MOTOR WIRING == Electronic Speed Controllers (ESCs) for electric motors or Throttle Servos for combustion motors can be connected in two ways: #'''In the receiver''' - Throttle port ''(Failsafe is handled by receiver)'' #'''In the Spirit unit''' - AUX (AUX1) port ''(Failsafe is handled by unit and/or additionally by receiver)'' Wiring details for each receiver type are described always in the particular scheme - see next sections. {{Info|[[File:info.png]] With Spektrum DSM2/X satellites throttle must be connected always to the unit.}} <p></p> {{Info|[[File:info.png]] By default Throttle output from the unit is disabled for all receiver types (except Spektrum DSM2/X). Assign '''Channel 1''' in the ''General/Channels - Throttle''.}} <p></p> In order to use [[Configuration#GOVERNOR|Governor]] it is always required to use Throttle output from the unit. ''Throttle frequency'' that can be configured in the unit can stay at default settings (60Hz). Only if Governor is used it is usefull to set as high frequency as possible. Recommended values are described in the [[Governor]] page. === Castle ESC === If Castle ESC is used, please configure following Throttle parameters in the ''General - Throttle/Governor'' window: *''Throttle Frequency:'' 60Hz. *''Throttle Range - Min.:'' 1060 us. *''Throttle Range - Max.:'' 1940 us. All other ESCs should work well with default settings. If not, please use the Factory default. === Throttle Servo === For combustion helicopters it is required to set optimal travel range in order to prevent a binding. If the servo is connected in the unit, you can set absolute limits that can never be exceeded. These can be configured in the ''General - Throttle/Governor - Throttle Range''. It is also possible that ''Throttle Reverse'' will be necessary to get fully closed condition when Throttle Hold is engaged. This will change servo movement direction. === µSpirit and Rudder ESC/Motor === µSpirit unit has full support for motor driven tail rotors. These motors are usually driven by a dedicated ESC. To control the motor standard servo signal is used. Connect Rudder ESC at the CH4 port. In the Setup Wizard it is necessary to set '''Rudder - Control type to Motor'''. Lastly make sure you will set Throttle range for this ESC. Please see description of the ''Rudder End-points'' in the [http://manual.spirit-system.com/index.php?title=Configuration#LIMITS_TAB Configuration/Limits tab] section. In order to turn off the Tail motor when Main motor is not running it is necessary to later assign the Throttle channel. See the Channels assignment in the [http://manual.spirit-system.com/index.php?title=Configuration#GENERAL Configuration/General - Channels] section. This can be changed anytime after the basic configuration. == CONNECTION OF STANDARD RECEIVER (PWM) == [[File:MPWM.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: PWM'' </center> [[File:pwms.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: PWM'' </center> [[File:pwm.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: PWM'' </center> [[File:pwm2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>''– receiver type: PWM'' </center> [[File:pwmgt.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: PWM'' </center> For standard receivers it is necessary to use two normal and one special cable. Three connectors from the special cable should be plugged into the receiver and the end of these cables to the unit. The unit is powered by two cables from the receiver. These are connected to the AUX and RUD positions. The Throttle (ESC or Throttle servo) should be connected to the receiver. The easiest way you can start is to connect a cable between the RUD port with Rudder output of the receiver. Then continue with the AUX port which should be connected to the Gyro Gain channel output of the receiver. Next, connect the Aileron, Elevator and Pitch channels. If you are not sure whether you have the correct output or not, you can plug in one servo and power the unit to verify that your connection is correct. This can be repeated for each servo. The Diagnostic tab in the software is very helpful too, because you can see whether the connection is correct even without connected servos. For Spektrum receivers you can view the [[Spektrum PWM connection]] scheme. {{Info|'''Spirit 2, Spirit Pro, Spirit GT'''<br/>The unit is able to control Bank Switching by 7th channel of the receiver. Connect the cable to the AUX2 port and allow Bank Switching in the software. }} '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' == CONNECTION OF SPEKTRUM DSM2/X SATELLITE == [[File:MSatellite.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: Spektrum DSM2/X'' </center> [[File:bind.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: Spektrum DSM2/X'' </center> [[File:Satellite.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: Spektrum DSM2/X'' </center> [[File:Satellite2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>'' – receiver type: Spektrum DSM2/X'' </center> [[File:SatelliteGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: Spektrum DSM2/X'' </center> Connection to a BEC is optional. If the model is powered by an external BEC, this must be connected to the RUD port. Also the power lead from the ESCs internal BEC must be disconnected. {{Info|'''Spirit'''<br/>A second satellite can be connected, but this can only be achieved via a special adapter connected to the RUD port. This adapter can be purchased separately. Before satellites can be used they must be bound to your transmitter, taking into account any failsafes that need to be set. To use both, two satellites and an external BEC, be sure to use a Y-harness made from large gauge wire to supply the high current that is needed.}} <p></p> {{Info|'''Spirit Pro, Spirit 2, Spirit GT'''<br/>You can connect two satellites directly to the unit. If you want to use only one satellite, you have to use the Primary (SAT-1) connector.}} To bind the satellites, insert a bind plug in the SYS port for DSM2 satellites or the ELE/PIT/AIL port for DSMX satellites. Power cycling the Spirit start the bind process. Once successfully bound, the STATUS LED will go out and the satellite LED will come on. If the second satellite fails to bind, swap the satellites and repeat the bind process. '''Be sure Receiver type in the software is configured to Spektrum DSM2/X otherwise binding process will not work. Never plug a connector for powering the unit to SYS or ELE/PIT/AIL positions.''' === Spektrum Multi Adapter === Spektrum Multi Adapter allows to connect additional 2 Spektrum DSM2/X satellites. It is suitable for all Spirit units and is recommended when using GeoLink module and/or ESC telemetry that is using a satellite ports. Before usage please bind satellites that are intended to be connected at the adapter through primary and secondary ports. [[File:Spektrum-Multi.jpg|class=smallwidth|center]] <center>'''Wiring'''</center> '''Servo cable''': RUD port<br/> '''Orange wire''': AIL pin {{Info|'''Spirit'''<br/> With this adapter it is possible to connect up to 3x Spektrum satellites at the same time.}} <p></p> {{Info|'''Spirit 2, Spirit Pro, Spirit GT'''<br/>With this adapter it is possible to connect up to 4x Spektrum satellites at the same time.}} == CONNECTION OF FUTABA S-BUS RECEIVER == [[File:MS-BUS.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: Futaba S-BUS'' </center> [[File:Spirit sbus.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: Futaba S-BUS'' </center> [[File:S-BUS.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: Futaba S-BUS'' </center> [[File:S-BUS2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>'' – receiver type: Futaba S-BUS'' </center> [[File:S-BUSGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: Futaba S-BUS'' </center> {{Info|'''Spirit'''<br/>When using S-BUS it is necessary to use an inverter that replaces the cable between the receiver and the Spirit unit's RUD port. The inverter cable - called '''SBUS Adapter''' - can be purchased separately. The SBUS Adapter has to be connected in the way, that longer end is directed to the unit and shorter to the receiver. This apply for both Futaba and FrSky receivers.}} <p></p> {{Info|'''μSpirit, Spirit Pro, Spirit 2, Spirit GT'''<br/>Connect the receiver with the unit by normal patch cable to the RUD port. You can use cable that is included in the package.}} Connection to a BEC is optional. For models of 500 size and larger it is recommended to use dual power supply cables due to the increased power consumption. That means besides the S-BUS cable, an additional power supply cable should be connected to the AUX port. When using this type of receiver you can connect the throttle cable directly to the receiver. Alternatively, you can assign the throttle channel in the software and use the AUX as throttle output from the unit. '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' == CONNECTION OF PPM RECEIVER == [[File:MPPM.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: PPM'' </center> [[File:Spirit_ppm.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: PPM'' </center> [[File:PPM.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: PPM'' </center> [[File:PPM2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>'' – receiver type: PPM'' </center> [[File:PPMGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: PPM'' </center> {{Info|[[File:info.png]] Connection to a BEC is optional. For models of 500 size and larger it is recommended to use dual power supply cables due to the increased power consumption. That means besides the communication cable, an additional power supply cable should be connected to the AUX port. }} When using this type of receiver you can connect the throttle cable directly to the receiver. Alternatively, you can assign the throttle channel in the software and use the AUX as throttle output from the unit. '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' {{Info|[[File:info.png]] Futaba pilots with PPM receiver such as R6107SP will need to reconfigure channels according [[Futaba PPM]] page. }} == CONNECTION OF JETI EX BUS RECEIVER == [[File:MEX-BUS.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: Jeti EX Bus'' </center> [[File:Spirit_exbus.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: Jeti EX Bus'' </center> [[File:EX-BUS.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: Jeti EX Bus'' </center> [[File:EX-BUS2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>'' – receiver type: Jeti EX Bus'' </center> [[File:EX-BUSGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: Jeti EX Bus'' </center> This connection type now supports the new integration with JETI Model transmitters. You can now fully configure the Spirit unit remotely through the JETI Model transmitter. Remember to configure the receiver type through the software or the integration will not work. Also, it is necessary to download Spirit.bin file from the website. Move the file to the Devices directory in the SD card of your transmitter. For futher instructions please check the [[Jeti Integration]] page. {{Info|[[File:info.png]] Connection to a BEC is optional. For models of 500 size and larger it is recommended to use dual power supply cables due to the increased power consumption. That means besides the EX Bus cable, an additional power supply cable should be connected to the AUX port. }} When using this type of receiver you can connect the throttle cable directly to the receiver. Alternatively, you can assign the throttle channel in the software and use the AUX as throttle output from the unit. '''A special cable is needed to enable this communication. Signal wire (Orange) is connected to the AIL pin, while power wires (Red and Brown) are connected to the RUD port in the unit. For JETI REX receivers, end of the special cable is connected to the EX1 or EX2 (depending on the receiver configuration). For EX receivers, please use EXT port.''' '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' == CONNECTION OF SRXL/SUMD RECEIVER == [[File:MSRXL.png|class=smallwidth|center]] <center> <span style="color:red">'''''μSpirit'''''</span>'' – receiver type: SRXL/SUMD'' </center> [[File:Spirit_srxl.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit'''''</span>'' – receiver type: SRXL/SUMD'' </center> [[File:SRXL.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit Pro'''''</span>'' – receiver type: SRXL/SUMD'' </center> [[File:SRXL2.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit 2'''''</span>'' – receiver type: SRXL/SUMD'' </center> [[File:SRXLGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: SRXL/SUMD'' </center> {{Info|[[File:info.png]] Connection to a BEC is optional. For models of 500 size and larger it is recommended to use dual power supply cables due to the increased power consumption. That means besides the communication cable, an additional power supply cable should be connected to the AUX port. This protocol family can work with a wide range of receivers. Thus you can use Multiplex SRXL, BeastX SRXL, [[Graupner SUMD]], Jeti UDI, Spektrum SRXL, JR X-Bus (mode B) and more. }} When using this type of receiver you can connect the throttle cable directly to the receiver. Alternatively, you can assign the throttle channel in the software and use the AUX as throttle output from the unit. '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' == CONNECTION OF FRSKY F.PORT RECEIVER == [[File:FPORTGT.png|class=halfwidth|center]] <center> <span style="color:red">'''''Spirit GT'''''</span>''– receiver type: FrSky F.Port'' </center> {{Info|[[File:info.png]] This protocol is supported by the most FrSky ACCST receivers. Presently F.PORT 1 generation is fully supported. It allows to carry channel, telemetry and integration data at the same time. Only Spirit GT units have support for this protocol. More details can be found at the [[FrSky FPort]] page. }} <p></p> {{Info|[[File:info.png]] Connection to a BEC is optional. For models of 500 size and larger it is recommended to use dual power supply cables due to the increased power consumption. That means besides the communication cable, an additional power supply cable should be connected to the AUX port. }} When using this type of receiver you can connect the throttle cable directly to the receiver. Alternatively, you can assign the throttle channel in the software and use the AUX as throttle output from the unit. '''Never plug a connector for powering the unit to SYS or ELE/PIT/AIL ports.''' <div class=noprint> ---- {|style="width: 100%;color: white;" |- | style="width: 33%;"| [[Installation|← Installation]] | style="width: 33%;text-align:center;"| [[#up|↑Up↑]] | style="text-align:right;" | [[Configuration|Configuration →]] |} ---- </div>
Navigation menu
Personal tools
English
Log in
Namespaces
Translate
Variants
Views
Language statistics
Message group statistics
Export
More
Search
Navigation
Main page
Recent changes
PDF Download
Tools
Special pages
Printable version