Binding Devo7e with Spektrum AR8000+sat

Hallo,
I am flying 3 different Walkera CPs with my Devo 7e with deviation 4.0.1 and I am quite happy with it.
Now I bought a used Mini-Protos with a kbar-Mini as gyro.
I have to buy a suitable receiver to get it bound to my Devo and thought of an AR8000.
Any suggestions/remarks?

What is your question? I dont understand what you're asking...

Edit:
Ok did a quick google search, it looks like the K-BAR is not a receiver at all, just a FBL gyro, so I assume what you're asking is how can you bind JUST the sat since a sat cant bind on it's own? Is that correct that's what you need?

If so buy yourself a orange or lemonRX rx with sat, way cheaper than OE Spektrum and works just as well. Absolutely no reason to buy a big, expensive real spektrum full RX just to use it one time to bind a sat.

Hi Rolf,

Do you already have a 7E hardware range mod?
Do you want to fly 450er helis with only ~7mW output power?

What Walkera CPs? 450er? Mini/Micro CPs?


You could use AR8000 with sat + TM1000.
AR8000 is bigger!! You may have to side-mount it instead of the back in the chassis.
That is what I use.

You could use AR6210 + SAT too.

Maybe TM1100. It is a bit smaller.

Half-Range AR6115e was used (back mounting in chassis) in Blade 450 3D.
But its a simple dipol with no antenna diversity or multiple receivers (e.g SAT).
Also works with TM1000.

You could also go the Spirit System FBL + BeastX Plus/Pro route with "Spektrum SRXL" digital signal and Spektrum AR9020: www.deviationtx.com/forum/3-feedback-que...-to-my-devo-rx#34212
www.deviationtx.com/forum/6-general-disc...t-to-deviation#29392

If you go the "Spektrum SAT only" route you will loose the Spektrum FlightLog telemetry feature.


Too many 3rd party RX threads around in various forums. Even in this. It may work or may not. You will find out that by crashing your heli.
IMHO not worth the price if you fly something which is not foam / EPP and is crash resistent.
Your heli replacement material and blades (+ FBL) will cost MORE than a good full-range receiver with Spektrum FlightLog support.

Thomas

Spektrum AR8000 is really a big one; I' ll take the AR6260. It' s not that wide.

Thanks for the extensive comments.
I'm flying Walkera's Super CP and Master CP as well as the V120D02S new.
I don't have any mods on my Devo 7e.
The idea of the Mini-Protos fell out the clouds.
It is a mayor step for ME with lots of uncertainities.
Will they (Devo 7e with deviation 4.0.1 and Spektrum AR 6260) bind?
How do I connect mini kbar with AR6260?
Where do I get the parameters in deviation 4.0.1 for a Mini-Protos, to hover in my garden?

Rolf wrote: I don't have any mods on my Devo 7e.

You really need to do extensive range testing on <10mw!!

I strongly suggest Devo 10 with 20dbm/100-150mw output power (hardware HF module) or modding your 7E when flying bigger planes/helis.

Rolf wrote: I'm flying Walkera's Super CP and Master CP aus well as the V120D02 new.

I am a little bit astonished that your 7E ~7mw output power even works with the MasterCP

Rolf wrote: The idea of the Mini-Protos fell out the clouds.
It is a mayor step for ME with lots of uncertainities.
Will they (Devo 7e with deviation 4.0.1 and Spektrum AR 6260) bind?

AR600, AR6210, AR8000 binds with DSMx.
Why should AR6260 not do that?

Rolf wrote: How do I connect mini kbar with AR6260?

Like any FBL.
You need to connect all servo cables (pass-thru) to the RX.
There should be a kbar manual.

ZYX FBL e.g uses one special 3-pin cable which routes one 3-port to 3x1 pin servo plugs (1 to 3 servo cable splitter).

You can probably not go the digital connection (e.g SUMD, S-Bus, SRXL) route with AR6260???
So connect all servo cables separately.

I am even not aware that Kbar/V-Stabi may support the proprietary "Spektrum SRXL" protocol like BeastX Plus/Pro and Spirit System do.

Rolf wrote: Where do I get the parameters in deviation 4.0.1 for a Mini-Protos, to hover in my garden?

FBL?
Easier as you do only need to have CCPM mixing set to "None", no active 120 CCPM.
Subtrimm 0.
Servo Travel 100%.

Or you may have to CALIBRATE subtrim/servo travels to your FBL (e.g ZYX requires that for exact travels and subtrim).


With FBL you CAN use the 6ch heli CCPM template (advanced GUI) and only adjust the mixers and travels to your needs.

Alternatively you could setup all channels manually from a CLEAN model yourself, bypassing the 3 pre-setup virtual channels.
But pre-defined pitch curves and dualrate/expo curves may help you to get started and understand DeviationTX a bit better.


Setting up helis mechanically and heli model in the transmitter as well as tweaking FBL parameters is a bigger step forward.
Take your time to learn it from the ground.

Personally I do believe just copying / importing model.ini files will N O T help you to get into the right direction.

Thomas.Heiss wrote: Too many 3rd party RX threads around in various forums. Even in this. It may work or may not. You will find out that by crashing your heli.
IMHO not worth the price if you fly something which is not foam / EPP and is crash resistent.
Your heli replacement material and blades (+ FBL) will cost MORE than a good full-range receiver with Spektrum FlightLog support.

Links to those? In particular, links to complaints about current (Orange RX ?20) or at least recent (?15) models? All the complaints I've seen are about the older ones. LemonRx doesn't have model numbers, so it's hard to say which are old and which aren't.

After all, there are people who will make the same recommendations about all Spektrum gear, because of the lack of diversity in the Rx's and public admission that Spektrum gear tends to brown out with normal wear and tear for aircraft.

Thanks for your comments.
I connected the AR6260 to the mini-kbar. I installed Vbar 5.3 in my computer. Devo 7e and AR6260 bind, and all five: Devo 7e, devention, AR6260, Mini kbar and Vbar 4.3 interact; but not as expected.
The engine does not react at all; the movements of the servos are wrong despite many parameter changes in Vbar 5.3 and deviation.

Post your model.ini Rolf.

You need to have Heli CCPM mixer set to "None" in DeviationTX.
Advanced GUI, simple GUI, advanced template or standard/simple heli template?

That leaves AUX1/pitch for N/R in the firmware.
Any Cyclic1-3 setups in your model.ini? Cyclic1/ELEV and Cyclic2/AIL may be swapped (e.g simple heli GUI)!!!

Do you have the right input mappings for ail and elev to the appropriate DSM output channels if manually setup your model without any heli template?

Have you walked thru the Howto FBL document here in the forum?


Rest (120 CCPM mixing configurations) and signs is vstabi stuff.
You might also wrongly connect servo cables from kbar to ar6260.


I think you need to find local support as remote diagnosis without overlooking everything is almost impossible.
Lets start with the model.ini.

Hey,
with your help the situation is improving.
Elevator and aileron are behaving normal. Pitch is behaving nearly normal.
But:
Rudder and pitch are moving in synchrony on throttle-stick. Gear-stick does' nt move anything.
The engine does not start at all.

Any suggestions?
Here is the file:

name=Mini Protos
mixermode=Advanced
[radio]
protocol=DSMX
num_channels=6
tx_power=150mW

[protocol_opts]
Telemetry=Off

[channel1]
template=complex
[mixer]
src=THR
dest=Ch1
curvetype=5point
points=-100,-20,30,70,90
[mixer]
src=THR
dest=Ch1
switch=FMODE1
curvetype=5point
points=80,70,60,70,100
[mixer]
src=THR
dest=Ch1
switch=FMODE1
curvetype=5point
points=100,90,80,90,100
[mixer]
src=THR
dest=Ch1
switch=HOLD1
scalar=-100
curvetype=fixed

[channel2]
reverse=1
template=cyclic1

[channel3]
template=cyclic2

[channel4]
template=expo_dr
[mixer]
src=RUD
dest=Ch4
[mixer]
src=RUD
dest=Ch4
switch=HOLD1
scalar=60

[channel5]
template=simple

[channel6]
template=cyclic3

[virtchan1]
template=expo_dr
[mixer]
src=AIL
dest=Virt1
curvetype=expo
points=45,45
[mixer]
src=AIL
dest=Virt1
switch=HOLD1
scalar=60
curvetype=expo
points=45,45

[virtchan2]
template=expo_dr
[mixer]
src=ELE
dest=Virt2
curvetype=expo
points=45,45
[mixer]
src=ELE
dest=Virt2
switch=HOLD1
scalar=60
curvetype=expo
points=45,45

[virtchan3]
template=expo_dr
[mixer]
src=THR
dest=Virt3
curvetype=5point
points=-30,-15,0,50,100
[mixer]
src=THR
dest=Virt3
switch=FMODE1
curvetype=5point
points=-100,-50,0,50,100
[mixer]
src=THR
dest=Virt3
switch=FMODE1
curvetype=5point
points=-100,-50,0,50,100

[trim1]
src=LEFT_V
pos=TRIMLV+
neg=TRIMLV-
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
[timer2]
type=countdown
time=10
[safety]
Auto=min
[gui-128x64]
V-trim=59,10,1
H-trim=5,59,3
V-trim=65,10,2
H-trim=74,59,4
Small-box=2,22,Ch3
Small-box=2,31,Timer1
Small-box=2,40,Timer2
Model=75,20
Battery=102,1
Toggle=4,10,0,3,0,None
Toggle=13,10,0,5,0,None
Toggle=22,10,0,4,0,None
Toggle=31,10,0,0,0,None
Toggle=40,10,0,0,0,None
TxPower=102,7
quickpage1=Telemetry monitor

Hey,
after hours of trying and improving and frustration I finally succeeded in getting the servos to work properly.
When I started the TX with full throttle before electrically initiating the bird, even the engine started.
Now it' s time to do a proper setup.

Hey,
the Mini-Protos is hovering in our garden. It has been a long way to get it airborne. But it' s worth it.
Thanks for your support.
Rolf