Advanced Search

I hope that a good compromise can be found for the required values for the servo travels.

I have seen that I have photographed an incorrect setting in the second picture on page 2 (Ail-Mix). Mux = add must be set here.

But in the ini file you are using it is programmed correctly, I have just checked it.

Hi - thanks for the latest model.ini. I now understand how to add the switch controlled flight mode! I also understand that a lot of my confusion has been with the deviationtx gui as implemented on the Devo 7E transmitter. The transmitter is small, very light and ideal for DLG, slope and the other disciplines I fly, but the gui is truly AWFUL!

I am still struggling with the very small amount of aileron movement offered by this mix. I have tried changing all of the curves for each of the channel mixes, both one at a time and in combination, but nothing seems to work. Today I'm starting with a fresh copy of your mix and will go through all of the settings yet again. I mean, it's cold outside and probably going to be raining all day, so what else is there to do!

Many thanks for all of your help with this.

Don

Here the ini-File.

Here is an overview of the CH3 mixer with all three pages. CH2 has exactly the same structure.

Donthemon wrote: I can adjust the amount of Elevator movement quite easily using the 'Subtrim' and 'Scale' adjustments in the simple and complex parts of the mix, but this also affects the amount of Aileron movement.The Aileron control surface movement is far too small and I cannot increase the amount of movement to what I need using any of the adjustments in either of the two channels, without making the elevator movement far too large.

Okay, I understand that. Here it is necessary to limit the deflection of Ele so that you still have the necessary reserve on the servo travel for Ail. This can be achieved, for example, with a curve that consists of 7 points in the simplest case (optimal for visualization). The Devo can have 13 points, so you can adjust the curve more optimally than in this example.

Here ist the ini-File with the Flight Mod function. Try it out

Hi - I made a mistake when I said that I had fully resolved the control movement problem. I have been playing about with so many different models to try and get this to work that I was looking at a different model.ini (which I broke and had to restore back...sighI)

So, I DO have the elevon control surfaces moving in the correct way (I use a mode 2 setup):

- Aileron stick moved right, the right hand elevon surface (that is, looking from behind, with the model pointing away from me) goes up and the left hand elevon surface goes down,
- Aileron stick moved left, the right hand elevon surface goes down and the left hand elevon surface goes up
- Elevator stick pushed forward (down elevator), both elevon surfaces go down
- Elevator stick pulled back (up elevator), both elevon surfaces go up

I have attached a picture so you can see the control surface layout

I can adjust the amount of Elevator movement quite easily using the 'Subtrim' and 'Scale' adjustments in the simple and complex parts of the mix, but this also affects the amount of Aileron movement.
The Aileron control surface movement is far too small and I cannot increase the amount of movement to what I need using any of the adjustments in either of the two channels, without making the elevator movement far too large.

So, while I still need a switch to drop both elevons a couple of mm, I still can't adjust the control surface movements in the way I need them.

Very confusing.

That's good that everything is now working as it should.

For fight mode, you need to add another page to the two complex mixers for CH 2 and Ch3, in which you use the “Add” command to add the desired value via the desired switch.

You are welcome to give me your current ini and I will program it for you. Then you can take a look at it and learn just like that

Hi - thanks for your Kunai model.ini, but I am obviously still missing something (or a lot of things).

However much I look at this, I just can't see how you would create this model.ini. With previous Graupner or JR transmitters, I would, for example, use menus to first select a flight mode, then select a channel to be changed, then make the change(s) I wanted and that would be it. Devo is obviously doing this in a very different way, and I just can't see how.

I think I understand, at least conceptually, how deviation works, with channel assignments, mixes to/from each channel, a flow of input channel -> mix(s) -> output channel. The trouble is that the Devo 7E gui is so awful to use (I tried loading the emulator, but couldn't get it to work properly), that I cannot see how to add a switch that will change the subtrim of a channel, without affecting the rest of the mix or doing nothing at all.

I can't be the only inexperienced deviation user with these problems, but I cannot find anything that explains how to do things like a setting above on a Devo 7E.

Any help, would be gratefully received.

Hi - sorry for not getting back to you, but I have hacked around with the model.ini and now seem to have all of the settings I need for channel and mixer scale and subtrim. So, many thanks for your help, really useful.

Do you know if there is anything anywhere that will show me how to use the Fmode switch as a flight mode switch? All of the posts I could find just say that it's really easy, but don't give any instructions. I just need to drop each elevon a couple of mm using a two position switch, then flick back to normal mode, but can't see how to do it.

Thanks

You have made a lot of effort!!!

Unfortunately, it only helps me to a limited extent with the implementation, because it is still not clear to me from the description and the very good graphics how, for example, the mechanical control of the servos on the elevons takes place, is the linkage at the top or bottom of the elevon...

Let's perhaps try it with the direction of the stick in conjunction with the channel monitor. Please complete the following example according to the required reaction. It would be sufficient if you want to assign the terms positive and negative accordingly:

Ele stick up = CH2 positive value
Ele stick up = CH3 positive value

Ele stick down = CH2 negative value
Ele stick down = CH3 negative value

Ail stick left = CH2 positive value
Ail stick left = CH3 negative value

Ail stick right = CH2 negative value
Ail stick right = CH3 positive value

Hi - see attached. I use mode 2 on the transmitter, so Aileron is the right hand transmitter stick moved side to side, Elevator is the right hand transmitter stick moved forward and backward.

So, with the model facing forward:
Aileron control moves right:
- right hand elevon goes up,
- left hand elevon goes down.
Aileron control moves left:
- right hand elevon goes down
- left hand elevon goes up.
Elevator control pulled back:
- both elevons move up
Elevator control pushed forward:
- both elevons move down

Basically, to make the newest model39.ini work, I made the following changes to the actual Alula model plane and the latest model39.ini :

- With the model facing forward, the left hand elevon servo is now connected to channel 3 on the receiver (Elevator)
- With the model facing forward, the right hand elevon servo is now connected to channel 2 on the receiver (Aileron)
- The Devo 7E gui AIL channel is reversed
- The Devo 7E gui ELE is reversed

Hope this makes sense.

Very pleased that it worked. Deviation is powerful there are many ways to achieve the goal.

(ii) swap the right hand wing servo plug from the Ele channel to the Ail channel on the receiver and the left hand wing servo plug from the Ail channel to the Ele channel on the receiver,

This would not be a problem to adapt in programming. Since I do not know how the servos are installed and which flaps is controlled with them. If you would like to create a small drawing showing the relationship between stick/direction and servo/direction, then I can adapt it.

Hi - you are a genius: it works!

I did have to:
(i) reverse both the Ail and Ele channels,
(ii) swap the right hand wing servo plug from the Ele channel to the Ail channel on the receiver and the left hand wing servo plug from the Ail channel to the Ele channel on the receiver,
(iii) change all of the scale and offset values in the complex mixes (no surprises there),
...but it works, so who cares?

You have succeeded in creating a simple elevon mixer where I and several other far more experienced deviation specialists have previously failed. I can stop using those virtual mixes!

Many thanks!

Hi - thanks for this new mix (moel39.ini). It is interesting as it goes back to why I (or actually, a deviation expert on the forum) had to build this elevon mix using virtual mixes, after I had worked on doing it for weeks and totally failed.

If you try and build the elevon mix using just complex mixes, what happens is exactly what is happening in your mix, that is, either:
- Elevon movement up and down (both surfaces go up and down together) is on the Ail stick
- Aileron movement left and right (one surface goes up and one goes down) is on the Elevator stick

If you try reversing the 'movement' in the Aileron simple section, this makes the Elevon(aileron) and Elevon(elevator) work on the correct stick BUT the aileron is reversed, that is right stick gives left aileron and left stick gives right right aileron.

You can then try swapping the servos around, or changing either of the AIL or ELE directions in the simple section, but you can never get both the Elevon Aileron (one surface up and one surface down) and Elevon Elevator (both surface up and down together) on the correct stick movement AND in the right direction.

The Devo expert who helped me said that this is why you need to use the virtual mixes, but I have to admit that I never understood any part of why. I was just grateful to have a working Elevon mix for my collection of deltas and flying wings.

Don

Hi Don try this one

Hi Don

I have loaded the model.ini of the Alula onto my Devo12s. My assumption is that the problems could be caused by the use of virtual channels. It could be that the assignment of the virtual channels is not assigned correctly due to the rearrangement. The programming of virtual channels is not necessary, as you can program several pages with a complex mixer.

I have written down the deflections of the servos Ail and Ele from the pop monitor and am rebuilding the programming of the ini file of the Alula on the basis of a DSM2 receiver.

Dirk

Attached is:

(a) the original model.ini I tried to convert from FrSKY to DSM2 - model6.ini
(b) the second much simpler model.ini that I also tried converting from FrSKY to DSM2 - model5.ini

For both of these conversion attempts, I first copied the original model.ini file(s) as references before making any changes. I then used a fresh copy of the model.ini for each new attempt at making changes, moving the channel order from the FrSKY AETR channel order to the DSM2 TAER channel order. I first tried using the Devo 7E gui (failed) and then started with a fresh reference copy to directly edit the model.ini file using Notepad(failed).

I have subsequently built a new Model5.ini from scratch, starting with an new, previously untouched template model.ini then adding the DSM2 binding, before adding the channel mixes. This worked and the model.ini looked exactly the same as the model.ini I ended up with when I tried to change from FrSKY to DSM2 using either the Devo 7E gui or directly editing the model.ini.

Baffling!

Would you like to attach the original ini file with the FrSky receiver here, then I can have a look at it.