Nano QX from Horizon

I would make these changes:
The strikethrough sections mean: remove for Devo7e if it wont tolerate FMODE2.
* FMODE2 is another flight mode valid on Devo10.
The attached file NanoQX.BMP (if you wish to use it) needs to be copied into modelico folder on transmitter.

name=Nano QX
mixermode=Advanced
icon=NANOQX.BMP
type=plane
[radio]
protocol=DSM2
num_channels=6
fixed_id=578918
tx_power=10mW

[protocol_opts]
Telemetry=Off

[channel1]
safetysw=Virt1
failsafe=-100
safetyval=-100
template=simple
[mixer]
src=THR
dest=Ch1

[channel2]
failsafe=0
template=expo_dr
[mixer]
src=AIL
dest=Ch2
curvetype=expo
points=20,20
[mixer]
src=AIL
dest=Ch2
switch=FMODE1
scalar=50
curvetype=expo
points=40,40
[mixer]
src=AIL
dest=Ch2
switch=FMODE2
scalar=80
curvetype=expo
points=20,20

[channel3]
failsafe=0
template=expo_dr
curvetype=expo
points=20,20
[mixer]
src=ELE
dest=Ch3
[mixer]
src=ELE
dest=Ch3
switch=FMODE1
scalar=50
curvetype=expo
points=40,40
[mixer]
src=ELE
dest=Ch3
switch=FMODE2
scalar=80
curvetype=expo
points=20,20

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

[channel6]
reverse=1
max=100
min=-100
scalar-=100
template=simple
[mixer]
src=Virt2
dest=Ch6
curvetype=3point
points=100,-100,100

[virtchan1]
name=TH-Hold
template=complex
[mixer]
src=Virt1
dest=Virt1
usetrim=0
curvetype=min/max
points=0
[mixer]
src=THR
dest=Virt1
offset=-1
usetrim=0
muxtype=add
[mixer]
src=AIL
dest=Virt1
switch=HOLD0
usetrim=0
curvetype=fixed

[virtchan2]
template=complex
[mixer]
src=FMODE0
dest=Virt2
scalar=3
usetrim=0
muxtype=add
[mixer]
src=Virt2
dest=Virt2
usetrim=0
muxtype=min
curvetype=fixed
[mixer]
src=AIL
dest=Virt2
scalar=-100
usetrim=0
muxtype=max
curvetype=fixed
[mixer]
src=AIL
dest=Virt2
switch=Virt3
usetrim=0
curvetype=fixed

[virtchan3]
template=complex
[mixer]
src=Virt3
dest=Virt3
offset=-1
usetrim=0
curvetype=min/max
points=0
[mixer]
src=!FMODE0
dest=Virt3
offset=-1
usetrim=0
muxtype=add
curvetype=min/max
points=0

[trim1]
src=LEFT_V
pos=None
neg=None
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
step=2
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
step=2
[timer1]
type=countdown
src=Ch1
resetsrc=HOLD0
time=300
[timer2]
type=permanent
src=Ch1
val=0
[safety]
Auto=min
FMODE0=max
[gui-128x64]
V-trim=55,10,1
H-trim=1,59,3
V-trim=69,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=79,30,Ch1
Bargraph=85,30,Ch2
Bargraph=91,30,Ch3
Bargraph=97,30,Ch4
Bargraph=103,30,Ch5
Bargraph=109,30,Ch6
Bargraph=115,30,Ch7
Bargraph=121,30,Ch8
Toggle=75,13,1,64,0,FMODE
Toggle=84,13,2,65,129,None
Toggle=93,13,0,5,0,None
Toggle=102,13,0,4,0,None
Toggle=111,13,0,8,0,None
Toggle=120,13,0,3,0,None
Battery=102,1
TxPower=75,1
quickpage1=Channel monitor
quickpage2=Mixer

I really appreciate you taking the time to do that, unfortunately the left toggle switch still cuts power completely. Also the one rate it has now is the slower rate instead of the fast rate. Thank you again for your help.

I have been attempting to edit the file myself with no luck, not quite at the level where I understand all that yet. Would love to get this to work so I dont have to use a spektrum transmitter, like the form factor of the 7e much better for this little quad.

Indigo, that's a great icon, thanks. I took the liberty of posting it over in www.deviationtx.com/forum/bw-icons-for-d...3-blade-nano-qx-icon , and gave you credit.

Hello,

for the Nano QX the improved protocol DSMX should be used instead of DSM2.

Greetings

Horst

Does anyone know if this will also work with the Nano QX FPV? I assume so, since the controllers are interchangeable.

Also, where can I find a list of all of these parameters and what they mean?

The Nano QX FPV doesn't change the flight control board or firmware, it just adds FPV gear to the QX. So the exact same config should be used.

There isn't a list for everything that's in a model.ini file. For the most part, you shouldn't be editing them directly, but using the UI in the transmitter. That's documented in the user manuals.

The community trades model.ini files to trade configs, and uses extracts from them to communicate settings information. They are pretty clear once you know your way around the UI on the transmitter. A lot of the stuff that's in the model.ini isn't used traded, because it's inconsequential. The trim settings are almost always the default values, timers are usually personal preference, as are most of the settings in the gui sections.

The exception is the [safety] section. That can't be edited in the UI. The default value is usually fine, but every once and while the default is wrong, or you want an extra value checked when you switch to a model. The parameters are Ch# or one of the inputs (depends on the Tx, and they are all over the UI). The possible values are Min, Zero and Max. They cause the Tx to complain when you switch to a model if the given channel or input doesn't have the named value.

I'm subscribing to this even though it's old. I used the ini from Fabian on page two as a starting point, www.deviationtx.com/forum/model-configs/...rizon?start=20#12197

and I modded the D/R switch to be reversed, since it was causing confusion when binding, and I thought it would be easier to deal with if it killed it in position 1.

for kicks, here's the ini I am currently running... I'm really new to deviation. if you have any pointers I'm all ears.

Is there anyway to setup a auto-flip for the QX using the TX? Wonder if a mix could be setup to switch to agility mode and apply aileron and then switch back to stability mode? I know its probably gonna be a trial and error type of thing but wonder if anybody has tried it?