Blade nano cpx Deviation 8s

Loaded all the models Tom has to offer, Checked the swash etc. It wants to do a hard nose dive on throttle up and a hard left pitch, So much so that trim and sub trim have not helped. The servos and everything seem fine.

PS, I know a little left pitch at throttle up (Mid Stick) is expected.

Hi, what models of mine have you loaded? Some of my models are for Walkera helicopters only and some are for Blade helicopters only.
The channel orders are different for Walkera and Blade.

Posted by: Hexperience

For Devo protocol on FBL controller:

ch1 Elevator stick position
ch2 Aileron stick position
ch3 Throttle stick position
ch4 Rudder stick position
ch5 -not used-
ch6 Collective Pitch (we'll call it stick position for now, more on that in a second)
ch7 Gyro setting

For DSM2/X protocol, the FBL will expect the same information from your tx, just in a different order.

ch1 Throttle stick position
ch2 Aileron stick position
ch3 Elevator stick position
ch4 Rudder stick position
ch5 Gyro setting (this channel is often called the Gear channel on the Rx)
ch6 Collective Pitch (we'll call it stick position for now, more on that in a second)


Also you can not change my model form the "Mixer GUI" from Advanced to Standard. It will reset (erase) my settings that I programmed.


I know you have Master CP and by the title of this post you also have a
Blade Nano CP X.


For trouble shooting I would download some other peoples models and see what happens.

It would help us if you posted a model you used and are having a problem with and list what helicopter you are using it for and with what transmitter.
It sounds like you have a setup issue on the helicopter or a transmitter setting that is not correct.

Tom,

It is a Blade nano CPX and yes I changed the Mixer. If I change it back to Advanced will I have to reload the model? I have not changed any channels before so we might be getting dangerous! I'm not sure which download I used but it was for the nano. There is usually two or more files on your downloads so I choose the one "I believe" is most recent. I use very little expo on my Walkeras and expo seems to do nothing on the Blade the way I have it set up now. It acts like I've got -100% expo.

Tom,

I switched it to advanced and I'm flying it in my bedroom with no problems. I'm so used to setting the DR/Expo/Pitch etc my self. I was not sure about the advanced settings. Even though I have my Master, Super and ladybird settings perfect. I'm going to download some more models and leave them advanced. I thank and appreciate you and this forum so much for helping me with a hobby I truly enjoy.

Your welcome.
That's great your flying now!
I am surprised that changing the "Mixer GUI" from Advanced to Standard which will reset (erase) my settings that I programmed and switching back brings my settings back. I just tried this here.

The Standard Mixer GUI doesn't have the extreme flexibility and options as the
Standard Mixer GUI does so that is why I use it and can make so many models for people with many features.

Most of my models cover v2.1, v3, and v4 firmware and the transmitters they are used for. That is why there is so many models posted.
I have made over 200 models so far...


If you want post the model of mine here that you need the DR and Expo settings changed and tell me what DR and Expo settings you want and I will change the settings for you and post the model here.

I will do that If I see a need. I knew that changing from advanced to standard would erase the model but apparently the reverse works fine. My test flight so far seems to be nothing more than learning a new hell. I like the DR and expo. I was under the expression that if my radio was a 4.0.1, I needed to look for that model, Is this not the case?

Correct, if your radio was v4.0.1 you would want to look for a v4 model. When I made the v3 models they were for specific model transmitters. Now with v4 I can make one model for all transmitters using my custom GUI.

Tom Z wrote: ...I am surprised that changing the "Mixer GUI" from Advanced to Standard which will reset (erase) my settings that I programmed and switching back brings my settings back. I just tried this here.

...me too. I have assumed that the model config is cleared more or less and the old advanced settings are overwritten. And as far as I remember it worked that way all the time (I usually use the advanced gui, just made some tests every now and then).
Maybe the model settings are not completely erased. I actually don't know if this would be good or bad since if some settings are lost the rest might lead to unpredictable behavior.
If I find some spare time I will take a look.

I must say that changing the settings helped tremendously, I'm not very empresses with this blade product. I can set low EXP on all my Walkeras but on this Blade It seems to go crazy with the slightest cyclic movement. This is a small hell I bought to fly inside and it seems to just go wherever it wants. I have checked everything but it just won't fly right. My Super CP does exactly what I transmit but this little Blade goes crazy at times. May be I got a Female,,,LOL

The Blade Nano CP X is SUPER twitchy! It is small and light with good power for it's size. Many people on the forums have a hard time controlling it and taming it down.
I would keep trying different DR and EXPO settings.

I just posted an Ultra Beginners model for the Walkera CP. It is very tame!
More tame than my Beginners model.
I might make one for the Blade and Align helicopter also.

rbe2012 wrote:

Tom Z wrote: ...I am surprised that changing the "Mixer GUI" from Advanced to Standard which will reset (erase) my settings that I programmed and switching back brings my settings back. I just tried this here.

...me too. I have assumed that the model config is cleared more or less and the old advanced settings are overwritten. And as far as I remember it worked that way all the time (I usually use the advanced gui, just made some tests every now and then).
Maybe the model settings are not completely erased. I actually don't know if this would be good or bad since if some settings are lost the rest might lead to unpredictable behavior.
If I find some spare time I will take a look.

Here is a model of mine. The first one is in the Advanced "Mixer GUI" and the second one was changed from the Advanced Mixer GUI to Standard Mixer GUI.
This model now has this message "Invalid model ini!".
Even though it said it reset the model changing from Advanced to Standard I see many of the settings from before are there. It also changed my 7 Point Curves to 9 Point Curves.




name=WalkeraMasterCP
mixermode=Advanced
icon=HELI.BMP
[radio]
protocol=DEVO
num_channels=7
tx_power=100mW

[protocol_opts]
Telemetry=Off

[channel1]
template=expo_dr
[mixer]
src=ELE
dest=Ch1
scalar=70
curvetype=expo
points=30,30
[mixer]
src=ELE
dest=Ch1
switch=ELE DR1
curvetype=expo
points=30,30

[channel2]
template=expo_dr
[mixer]
src=AIL
dest=Ch2
scalar=70
curvetype=expo
points=30,30
[mixer]
src=AIL
dest=Ch2
switch=AIL DR1
curvetype=expo
points=30,30

[channel3]
safetysw=RUD DR1
safetyval=-100
template=complex
[mixer]
src=THR
dest=Ch3
curvetype=7point
points=-100,-66,-33,0,33,66,100
[mixer]
src=THR
dest=Ch3
switch=FMODE1
curvetype=7point
points=100,93,86,80,86,93,100
[mixer]
src=THR
dest=Ch3
switch=FMODE2
curvetype=fixed

[channel4]
template=simple
[mixer]
src=RUD
dest=Ch4

[channel6]
template=complex
[mixer]
src=THR
dest=Ch6
usetrim=0
curvetype=7point
points=-15,-10,-5,0,18,36,54
[mixer]
src=THR
dest=Ch6
switch=FMODE1
usetrim=0
curvetype=7point
points=-54,-36,-18,0,18,36,54
[mixer]
src=THR
dest=Ch6
switch=FMODE2
usetrim=0
curvetype=7point
points=-54,-36,-18,0,18,36,54

[channel7]
template=complex
[mixer]
src=Ch7
dest=Ch7
scalar=60
curvetype=fixed
[mixer]
src=Ch7
dest=Ch7
switch=FMODE1
scalar=60
curvetype=fixed
[mixer]
src=Ch7
dest=Ch7
switch=FMODE2
scalar=60
curvetype=fixed

[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
[datalog]
switch=None
rate=1 sec
[safety]
Auto=min
[gui-320x240]
V-trim=129,75,1
H-trim=4,220,3
V-trim=181,75,2
H-trim=191,220,4
Big-box=8,40,Ch1
Small-box=8,95,Timer1
Small-box=8,133,Timer2
Small-box=8,172,Timer3
Bargraph=200,150,Ch1
Bargraph=214,150,Ch2
Bargraph=228,150,Ch3
Bargraph=242,150,Ch4
Bargraph=256,150,Ch5
Bargraph=270,150,Ch6
Bargraph=284,150,Ch7
Bargraph=298,150,Ch8
Toggle=144,36,1,64,128,FMODE
Toggle=144,69,2,65,129,MIX
Toggle=144,102,5,68,0,ELE DR
Toggle=144,135,4,67,0,AIL DR
Toggle=144,168,3,66,0,RUD DR
Toggle=144,201,8,71,0,GEAR
Model=207,40







name=WalkeraMasterCP
mixermode=Standard
icon=HELI.BMP
[radio]
protocol=DEVO
num_channels=7
tx_power=100mW

[protocol_opts]
Telemetry=Off

[channel1]
template=cyclic2

[channel2]
template=cyclic1

[channel3]
safetysw=RUD DR1
safetyval=-110
template=complex
[mixer]
src=THR
dest=Ch3
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=THR
dest=Ch3
switch=FMODE1
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=THR
dest=Ch3
switch=FMODE2
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100

[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=AIL
dest=Virt1
curvetype=expo
points=0,0
[mixer]
src=AIL
dest=Virt1
switch=FMODE1
curvetype=expo
points=0,0
[mixer]
src=AIL
dest=Virt1
switch=FMODE2
curvetype=expo
points=0,0

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

[virtchan3]
template=complex
[mixer]
src=THR
dest=Virt3
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=THR
dest=Virt3
switch=FMODE1
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=THR
dest=Virt3
switch=FMODE2
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=THR
dest=Virt3
switch=!RUD DR0
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=Ch3
time=180
[timer2]
src=Ch3
[datalog]
switch=None
rate=1 sec
[safety]
Auto=min
[gui-320x240]
V-trim=129,75,1
H-trim=4,220,3
V-trim=181,75,2
H-trim=191,220,4
Big-box=8,40,Ch1
Small-box=8,95,Timer1
Small-box=8,133,Timer2
Small-box=8,172,Timer3
Bargraph=200,150,Ch1
Bargraph=214,150,Ch2
Bargraph=228,150,Ch3
Bargraph=242,150,Ch4
Bargraph=256,150,Ch5
Bargraph=270,150,Ch6
Bargraph=284,150,Ch7
Bargraph=298,150,Ch8
Toggle=144,36,1,64,128,FMODE
Toggle=144,69,2,65,129,MIX
Toggle=144,102,5,68,0,ELE DR
Toggle=144,135,4,67,0,AIL DR
Toggle=144,168,3,66,0,RUD DR
Toggle=144,201,8,71,0,GEAR
Model=207,40

There is another thread concerning the same problem:
Error message when i try accessing my pitch curves
I think there is something strange with evaluating the mixers, but I never went deep into mixer programming so I am not really able to find the error.
My first guesses:
- FMODE switch positions counted wrong - doesn't seem so
- TH switch status calculated wrong - didn't manage to verify
- model config not completely cleared when switching to standard gui - not verified

Someone should file a ticket on bitbucket.