- Posts: 63
Setting up a DLG flying wing on a 7e.
- VTdev
- Topic Author
- Offline
Protocol is DSM2 mode 2. Receiver is a Lemon RX 6 channel. Deviation version is devo7e-v4.0.1-6a63c8e
The first step was to get elevons working. The following was the basic setup of channels 2 and 3 which worked for that:
[channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
scalar=40
[mixer]
src=!ELE
dest=Ch2
scalar=35
muxtype=add
[channel3]
template=complex
[mixer]
src=ELE
dest=Ch3
scalar=35
[mixer]
src=AIL
dest=Ch3
scalar=40
muxtype=add
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
This seemed to work well. Next thing I'd like is to add 14% up pitch when HOLD1 is present.
So first question, what is the most economical way to do that?
Do I copy both elevon channel codes twice, once for HOLD0 and once for HOLD1 with an offset for the latter in the appropriate mix pages or is there a cleaner way?
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
However, it isn't very clean (for instance is it necessary to explicitly specify switch Hold0 ?) Is there anything that could be cut out?
And I'm a little confused by the fact that the 14% offset is applied to the AIL mix pages instead of the ELE mix pages, since pitch is what the switch trims.
Yet it works.
Any clarification would be appreciated, though...
channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
switch=HOLD0
scalar=40
[mixer]
src=!ELE
dest=Ch2
switch=HOLD0
scalar=35
muxtype=add
[mixer]
src=AIL
dest=Ch2
switch=HOLD1
scalar=40
offset=14
[mixer]
src=!ELE
dest=Ch2
switch=HOLD1
scalar=35
muxtype=add
[channel3]
template=complex
[mixer]
src=ELE
dest=Ch3
switch=HOLD0
scalar=35
[mixer]
src=AIL
dest=Ch3
switch=HOLD0
scalar=40
muxtype=add
[mixer]
src=ELE
dest=Ch3
switch=HOLD1
scalar=35
[mixer]
src=AIL
dest=Ch3
switch=HOLD1
scalar=40
offset=-14
muxtype=add
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
Answer: It does.
Example:
This:
[channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
scalar=40
[mixer]
src=!ELE
dest=Ch2
scalar=35
muxtype=add
[mixer]
src=AIL
dest=Ch2
switch=HOLD1
scalar=40
offset=14
[mixer]
src=!ELE
dest=Ch2
switch=HOLD1
scalar=35
muxtype=add
Appears to be equivalent to this:
channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
switch=HOLD0
scalar=40
[mixer]
src=!ELE
dest=Ch2
switch=HOLD0
scalar=35
muxtype=add
[mixer]
src=AIL
dest=Ch2
switch=HOLD1
scalar=40
offset=14
[mixer]
src=!ELE
dest=Ch2
switch=HOLD1
scalar=35
muxtype=add
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
And the pitch response from a 1-to-1 curve to an expo curve of 35.
I don't need these rates switched in and out, but I want them present whether HOLD1 is active or not, so I added them to all 8 mix pages.
That ended up looking like this in the model.ini file:
[channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
scalar=40
curvetype=expo
points=15,15
[mixer]
src=!ELE
dest=Ch2
scalar=35
muxtype=add
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch2
switch=HOLD1
scalar=40
offset=14
curvetype=expo
points=15,15
[mixer]
src=!ELE
dest=Ch2
switch=HOLD1
scalar=35
muxtype=add
curvetype=expo
points=35,35
[channel3]
template=complex
[mixer]
src=ELE
dest=Ch3
scalar=35
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch3
scalar=40
muxtype=add
curvetype=expo
points=15,15
[mixer]
src=ELE
dest=Ch3
switch=HOLD1
scalar=35
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch3
switch=HOLD1
scalar=40
offset=-14
muxtype=add
curvetype=expo
points=15,15
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
Maybe there's a simpler way I'm not seeing that someone could suggest?
The requirements are:
Elevons
Pitch scaled to 35%
Roll scaled to 40%
Pitch expo 35
Roll expo 15
A switch that adds 14% up pitch when active.
I have my Spektrum DX6i already set up to provide the same requirements.
By comparison, changing expo, or scale on any control, or offset for the (flap) switch, requires changing only one number in each case, and is active as soon as changed (does not require saving). It is also easier to see at a glance what the current settings are, without navigating to multiple pages to check them.
I should say that the DX6i does have a bug in its elevon mix firmware, so I did have to ignore that pre-set mix, and mix the elevons manually to get what I wanted, as a workaround.
So, question -- is it possible to do a simpler setup with Deviation software, than the one I came up with for these requirements, and one that is easier to change in the field, with less chance of error?
Thanks!
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
I've attached the icon below.
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
It seemed ELE should be the source since it was a pitch control. But I wasn't able to get that to work yesterday. So AIL was used as the source -- only because for some reason I couldn't understand it seemed to work when the other didn't.
I think now that was caused by the fact that every time you make a change you have to save it to make it active, and while trying to work it out, I may not have saved once. Also, an ELE and AIL can conflict in an elevon mix, if of opposite sign. Flipping the HOLD1 switch can conceivably tell one of the elevon servo's channels to move in two opposite directions -- netting out to no movement. And so looking like a recent change has no effect.
Anyway, I decided to retry getting the Hold1 to source its offset from ELE rather than AIL, by carefully entering the changes and saving every time I altered a value. And it worked.
So here is the corrected Elevon section of the model.ini. The older version worked, but this one makes better sense.
[channel2]
template=complex
[mixer]
src=AIL
dest=Ch2
scalar=40
curvetype=expo
points=15,15
[mixer]
src=!ELE
dest=Ch2
scalar=35
muxtype=add
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch2
switch=HOLD1
scalar=40
curvetype=expo
points=15,15
[mixer]
src=!ELE
dest=Ch2
switch=HOLD1
scalar=35
offset=14
muxtype=add
curvetype=expo
points=35,35
[channel3]
template=complex
[mixer]
src=ELE
dest=Ch3
scalar=35
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch3
scalar=40
muxtype=add
curvetype=expo
points=15,15
[mixer]
src=ELE
dest=Ch3
switch=HOLD1
scalar=35
offset=-14
curvetype=expo
points=35,35
[mixer]
src=AIL
dest=Ch3
switch=HOLD1
scalar=40
muxtype=add
curvetype=expo
points=15,15
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
1.) In a model.ini are line breaks significant? Or can I add some blank lines to increase readability?
2.) Are comments allowed -- and if so how are they delimited?
3.) Is there a size limit for the file that I need to be aware of if doing any of the above?
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
Line breaks don't seem to interfere with function in a model.ini.
No idea about file size limitations.
Moving this discussion to RCGroups.
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- VTdev
- Topic Author
- Offline
- Posts: 63
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- rbe2012
- Offline
- So much to do, so little time...
- Posts: 1433
So using a commented file as a template allows you to use more than 4096 bytes (characters) - when used for a model the comments are cleaned upo and the file should fit into the 4096-sized modelXX.ini file.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- General
- General Discussions
- Setting up a DLG flying wing on a 7e.