How To Set Up SAFE Mode Using Standard GUI

Looking at this I have no idea where half of that came from. I did it in standard, then switched to advanced as Thomas suggested. I did not do this in the standard GUI.

I thought i was getting this, but clearly I am not.

Jim

name=Nano CP S
mixermode=Standard
[radio]
protocol=DSMX
num_channels=7
tx_power=100mW

[protocol_opts]
Telemetry=Off

[channel1]
template=complex
[mixer]
src=THR
dest=Ch1
curvetype=9point
points=20,35,50,65,80,80,80,80,80
[mixer]
src=THR
dest=Ch1
switch=FMODE1
curvetype=9point
points=80,80,80,80,80,80,80,80,81
[mixer]
src=THR
dest=Ch1
switch=FMODE2
curvetype=9point
points=80,80,80,80,80,80,80,80,80

[channel2]
template=cyclic1

[channel3]
template=cyclic2

[channel4]
template=expo_dr
[mixer]
src=RUD
dest=Ch4
curvetype=expo
points=0,0
[mixer]
src=RUD
dest=Ch4
switch=FMODE1
curvetype=expo
points=0,0
[mixer]
src=RUD
dest=Ch4
switch=FMODE2
curvetype=expo
points=0,0

[channel6]
template=cyclic3

[channel7]
template=expo_dr
[mixer]
src=MIX0
dest=Ch7
scalar=40
curvetype=fixed
[mixer]
src=MIX0
dest=Ch7
switch=MIX1
scalar=0
curvetype=fixed
[mixer]
src=MIX0
dest=Ch7
switch=MIX2
scalar=-100
curvetype=fixed

[virtchan1]
template=expo_dr
[mixer]
src=ELE
dest=Virt1
curvetype=expo
points=0,0
[mixer]
src=ELE
dest=Virt1
switch=FMODE1
curvetype=expo
points=0,0
[mixer]
src=ELE
dest=Virt1
switch=FMODE2
curvetype=expo
points=0,0

[virtchan2]
template=expo_dr
[mixer]
src=AIL
dest=Virt2
curvetype=expo
points=0,0
[mixer]
src=AIL
dest=Virt2
switch=FMODE1
curvetype=expo
points=0,0
[mixer]
src=AIL
dest=Virt2
switch=FMODE2
curvetype=expo
points=0,0

[virtchan3]
template=complex
[mixer]
src=THR
dest=Virt3
curvetype=9point
points=-6,-3,0,3,6,6,8,10,12
[mixer]
src=THR
dest=Virt3
switch=FMODE1
curvetype=9point
points=-6,-4,-2,0,3,5,7,9,12
[mixer]
src=THR
dest=Virt3
switch=FMODE2
curvetype=9point
points=-5,-3,0,2,5,28,52,76,100
[mixer]
src=THR
dest=Virt3
switch=!GEAR0
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,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-
[timer1]
type=countdown
src=Ch1
resetsrc=!MIX1
time=180
[timer2]
src=Ch1
[datalog]
switch=None
rate=1 sec
[safety]
Auto=min
Ch1=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,RUD DR
Toggle=13,10,0,5,0,ELE DR
Toggle=22,10,0,4,0,AIL DR
Toggle=31,10,0,0,0,None
Toggle=40,10,0,0,0,None
TxPower=102,7
quickpage1=Telemetry monitor

This is the problem with starting with the standard GUI. It always sets up a cyclic mix like this. For everything but flybar'ed helis, you don't need that. I'm not quite sure what problem you're having, so won't try and a suggest a fix for that.

Here is what I would do to clean this up. I'm not suggesting you do this, but offer it in the hope that it'll help you figure or what's going on.

First, change channels two and three to Expo&DR mixes. That's AIL and ELE, in that order. Unlike the standard GUI, you'll have to set them up individually. Virtual channel three looks like a pitch channel, except it has four settings, with GEAR1 overriding the FMODE switch. If that's actually what you want, use the channel reorder feature to move this to channel 6. Make sure you don't move channel 7, and finally set what used be channel 6 and virtual channels 1 and 2 to None, since they are no longer needed.

Thanks mwm, but what you just said means nothing to me. I guess I am just not computer literate. I know what the ini to look like, so I have asked a friend, who does understand, to write the ini for me.

My question is this. The "standard" GUI is very clear. Look at it for a minute or two and it is clear what to do. The "advanced" GUI is much more powerful, but very confusing. Not user friendly at all. Why couldn't it have been written differently?? More like the "standard".

Jim

No, STOP!
Make a USB backup first!!

And leave Virt1 and Virt2
They are already setup with D/R by the heli template which works.
You just have to use the COL-AIL and COL-ELEV channels to modify DR. Works perfectly fine for me.

No, don`t change CH2/CH3 as they point to Cyclic1 and 2 which already work.
Dont change things anymore which work already.


You may want to start over loading the 6CH advanced heli template (not standard) in the setup menu (Load...) as your pitch curves are wrong and see how it works (missing SAFE on CH5 so).

Probably it is better to just DL the Nanocps from model request section if you want to go with the advanced GUI, if there is any tested one...I have none...
Or DL a working/tested model copy of Nanocpx and just add CH5/GEAR SAFE mix switch.

Otherwise just try directly swapping Cyclic1 and Cyclic2 in the model.ini but not changing from standard to advanced in model setup.


IMHO there are multiple errors (taken over from standard GUI):
1) SAFE is setup on CH7 with MIX switch (gyro gain standard menu) instead of CH5/GEAR.
This is probably the reason why it stays in agility mode.
You have to check the Blade Nanocps manual. Max channels is probably 6, not 7-8?! Would have to review myself...

2) CYC-COL pitch curves for FMode0,1,2:
points=-6,-4,-2,0,3,5,7,9,12

What shall that be??
What is the point of -6? You either want to to have full negative pitch or max -3 to -4 degree.

You complain about collective not to be working but you miss to set correct -100 and +100 endpoints. You already did that in the standard GUI?!?
I understand that you wanted to set pitch to those exact degree values.
But it is of course NOT working like that! Neither on Deviation, nor on Spektrum Airware firmware.

-12/14 = -100
+12/14 = +100
0 degree = 0 in advanced mixer

On Spektrum Airware you have 0, 50, 100 instead of -100/+100.
Standard GUI is more like Airware if I remember correctly?

---

I suggest this standard linear pitch and tweaking to your needs:
-100 - -75 - -50 - -25 - 0 - +25 - +50 - +75 - +100


Honestly I do even think that 9-Point is not the right curve for you
A little bit more complicated, too many (not self adjusting) mid points. Only standard GUI has self adjusting points - point curve editor is better IMHO on standard (different thing).

Default linear 5-Point pitch:
-100 - -50 - 0 - +50 - +100 =
0 - 25 - 50 - 75 - 100

---

Somewhere on helifreak.com I had posted to 2-3 Blade threads about pitch curve suggestions, tuning, limiting negative pitch 30/40 instead of 0 (Spektrum Airware) and how to re-calculate 0..100 values to -100...+100 curves.
Mabye I find them to link here...probably not


If you want to limit negative pitch as a heli beginner I suggest not go go over -3 (=-25%) to -4 degree: 30/40 cuve settings worked for me.

Instead of 0 25 50 75 100 for Spektrum airware:
30 40 50 75 100
Or
40 45 50 75 100

Re-calculated:
30 x 2 -100 = -40
40 x 2 - 100 = -20

-40 -30 -20 -10 - 0 - 25 50 75 100
Or
-20 -15 -10 -5 - 0 - 25 50 75 100

There had been 1-2 threads about this GUI stuff not a long time ago (sorry I don't remember exact thread names for a link....would have to search myself).
No need to start it here over again (wrong topic).


Honestly Jim, if you want a standard GUI which is more powerful than DeviationTX standard GUI you simply just need to buy a Spektrum DX6G3/DX8G2/DX9....too bad you run into the cyclic thing on the standard GUI...

Spektrum DX18 was re-written from first DX8G1 Airware.
They added free channel mapping, free switch select, powerful glider program which supports 10 flightmodes and complex 2-3 switch assignment (starting at 5 FM).

But they limit programmable mixers depending on transmitters 5/8/10/16 (16 only on DX18).


DeviationTX on the other hand is programmed like this to be most flexible and have almost endless of possibilities combining virtual channels + complex mixers (which DX8 had not beyond 8 channels).

You can`t buy a Frsky Taranis with OpenTX firmware and wonder where all those fancy Spektrum Airware menues are which you would have to pay 330-500euro and above for.

Fency menu = very limited and not extensible for complexer tasks


I once had started a thread about what features to take over from the standard mixer GUI (like more powerful curve editor). I pretty much hate those -100 to +100 values for throttle channel as you manually have to re-calculate.

Jim here is the thread about the Nano CPS model config: www.deviationtx.com/forum/model-configs/4926-blade-nano-cp-s

You may run into a pitch curve problem: www.deviationtx.com/forum/3-feedback-que...o-cp-s-pitch-problem

I will try to ask my dealer if he has a Nano test heli which I could borrow to program it.
He probably can not give me one from the ready-to-buy packages he wants to sell.

Well, I still have my NanoCPX heli model file, but I would need to adopt for CH5/GEAR SAFE mode or I need to test this NanoCPS model.ini file from the model config section...

Thanks for all the help. I did not realize that there were limitations in programming capabilities caused by making a more readable format. I'll just have to figure this out some how.

I like the idea of being able to fly all my heli's off one transmitter, which Deviation allows you to do. It is a very good program, just a bit confusing to those of us with limited computer knowledge.

Jim

Thomas nailed this one: the advanced GUI is different because we want it to be more powerful. While we realize that this makes it unusable for some people (the OpenTx was described by one hobbyist as "requiring a CS degree", and DeviationTx isn't any simpler), there are lots of option for those people.

Improving the standard GUI seems like the perfect thing to set up a software bounty for. There are web sites that handle such if someone wanted to do that.. But I never use that GUI, so have no interest in doing so.

The other option would be an OpenTx transmitter. The problem there is that - except for the Taranis - they are cheap in every sense of the word. You'd then want to use the DIY multi protocol module to get to a variety of protocols. At this point, I believe it's using the deviationTx protocols directory as is for protocol support. it doesn't have a "standard" GUI, but has a companion desktop application to help set things up.

mwm wrote: Thomas nailed this one: the advanced GUI is different because we want it to be more powerful. While we realize that this makes it unusable for some people (the OpenTx was described by one hobbyist as "requiring a CS degree", and DeviationTx isn't any simpler), there are lots of option for those people.

Improving the standard GUI seems like the perfect thing to set up a software bounty for. There are web sites that handle such if someone wanted to do that.. But I never use that GUI, so have no interest in doing so.

The other option would be an OpenTx transmitter. The problem there is that - except for the Taranis - they are cheap in every sense of the word. You'd then want to use the DIY multi protocol module to get to a variety of protocols. At this point, I believe it's using the deviationTx protocols directory as is for protocol support. it doesn't have a "standard" GUI, but has a companion desktop application to help set things up.

This thread has been most helpful in many ways. I am new to the hobby and have been feeling my way along. I saw folks talking about Deviation, it sounded good, so I bought a Devo 10 and attempted to dive right in. I had no idea, because nobody had said, how difficult it is to understand. Now I understand more about it. You all are not a commercial company for profit, like Spectrum. You have designed a powerful program, but you neither gain, nor lose anything if people can or can not use it, so nobody really cares. I can not fault your thinking in any way, nor would i try to.

With that said, I know exactly what pitch/throttle curves I want and how I want my ini to look. I have it all written down, but simply can not get it in the tx. Therefore, I would be more than happy to PAY someone to write the file for me.

Jim

post what you have written down, ie what you want to have happen for switches and curves etc, and i'll setup a base ini for you. i don't understand why you don't just use one of the existing ini's for this heli though?

I am pretty sure if the one I posted on the first page of this thread is edited to match the Devo 10 switches it will work just fine. I got it from here but it was for the Devo 8 so edited it to work on my 7E.

That is very kind of you HH. Thanks.

Jim

-25 0 +25 +30 +40 +50 +60 +70 +75 ( A nine point curve) (Same on all three FMOD settings)

Throttle Curve: On FMOD Switch

FMOD "0" = 75 straight across.

FMOD1 = 85 straight across

FMOD2 = 100 straight across

DR/EXPO: On the ELEV Switch

0 = DR=75 Expo=15 (Low)

1 = DR = 100 Expo = 15 (High)

Throttle Hold = Rudder DR

SAFE/Agility = Gear Switch

Timer: Set for 5 Minutes

On/Off with TH

Reset = AILE DR

I haven't forgot about you bud, just been enjoying the nice weather we're having, I'll try to get it done this evening

HappyHarry wrote: I haven't forgot about you bud, just been enjoying the nice weather we're having, I'll try to get it done this evening

Not a problem HH. Enjoy the weather while ya can.

I did attempt some programing. Can't get the throttle to arm when I flip off TH. Als can no get stability or agility mode to work. Could you look at what i have done and point me in the correct direction??

Thanks,

Jim


name=Blade nCPs
mixermode=Advanced
icon=HELI.BMP
[radio]
protocol=DSMX
num_channels=7
tx_power=150mW

[protocol_opts]
Telemetry=Off

[channel1]
safetysw=RUD DR1
safetyval=-100
template=complex
[mixer]
src=THR
dest=Ch1
switch=FMODE0
curvetype=3point
points=75,75,75
smooth=1
[mixer]
src=THR
dest=Ch1
switch=FMODE1
curvetype=3point
points=95,95,95
smooth=1
[mixer]
src=THR
dest=Ch1
switch=FMODE2
curvetype=3point
points=100,100,100
smooth=1

[channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
switch=MIX0
scalar=75
curvetype=expo
points=15,15
[mixer]
src=AIL
dest=Ch2
switch=MIX1
scalar=95
usetrim=0
curvetype=expo
points=15,15
[mixer]
src=AIL
dest=Ch2
switch=MIX2
usetrim=0
curvetype=expo
points=15,15

[channel3]
template=complex
[mixer]
src=ELE
dest=Ch3
switch=MIX0
scalar=75
curvetype=expo
points=15,15
[mixer]
src=ELE
dest=Ch3
switch=MIX1
scalar=95
curvetype=expo
points=15,15
[mixer]
src=ELE
dest=Ch3
switch=MIX2
usetrim=0
curvetype=expo
points=15,15

[channel4]
template=complex
[mixer]
src=RUD
dest=Ch4
switch=MIX0
scalar=75
curvetype=expo
points=15,15
[mixer]
src=AIL
dest=Ch4
switch=MIX1
scalar=95
usetrim=0
curvetype=expo
points=15,15
[mixer]
src=RUD
dest=Ch4
switch=MIX2
usetrim=0
curvetype=expo
points=15,15

[channel5]
template=simple
[mixer]
src=ELE DR0
dest=Ch5

[channel6]
subtrim=4
template=complex
[mixer]
src=THR
dest=Ch6
switch=FMODE0
curvetype=9point
points=-25,0,25,30,40,50,60,75,85
smooth=1
[mixer]
src=THR
dest=Ch6
switch=FMODE1
curvetype=5point
points=-100,-50,0,50,100
smooth=1
[mixer]
src=THR
dest=Ch6
switch=FMODE2
curvetype=9point
points=-25,0,25,30,40,50,60,75,85
smooth=1

[channel7]
template=simple
[mixer]
src=GEAR0
dest=Ch7

[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-
[timer1]
src=Ch1
[timer2]
type=countdown
src=Ch1
time=300
[datalog]
switch=None
rate=1 sec
[safety]
Auto=min
[gui-128x64]
V-trim=54,10,1
H-trim=1,59,3
V-trim=71,10,2
H-trim=78,59,4
Big-box=2,12,Ch1
Small-box=2,28,Timer1
Small-box=2,38,Timer2
Small-box=2,48,Timer3
Bargraph=81,30,Ch1
Bargraph=95,30,Ch2
Bargraph=102,30,Ch3
Bargraph=109,30,Ch4
Bargraph=115,30,Ch5
Bargraph=88,30,Ch6
Bargraph=122,30,Ch7
Toggle=61,12,1,64,128,FMODE
Toggle=114,13,4,67,0,AIL DR
Toggle=99,13,5,68,0,ELE DR
Toggle=84,13,2,65,129,MIX
Toggle=61,29,9,72,0,RUD DR
Toggle=61,45,8,71,0,GEAR
Battery=102,1

a quick glance shows your throttle safety value at -100, is this low enough to arm the throttle normally? try changing it to -110, and for ch5 it should be set to a min/max curve, as -100 will be stability and +100 agility (or vice versa)

HappyHarry wrote: a quick glance shows your throttle safety value at -100, is this low enough to arm the throttle normally? try changing it to -110, and for ch5 it should be set to a min/max curve, as -100 will be stability and +100 agility (or vice versa)

I changed the safety value to -110. With he throttle all the way down I get nothing, but when I move it forward a tad the motor arms, but I have zero collective.

For channel 5 I changed it to min/max, but it would only let me put in "one" value".

I might be getting close. Stick with me HH.

Jim

try this bud,

Thank you sir.

Jim

no problem, is it working ok as you expected?

Just loaded it HH.

TH = Works

Elev DR = Stability mode or shuts motor off

Cyclic = Full response

Gear = Nothing

Mix = Nothing

FMODE = Nothing

Collective = Nothing