OpenTX example of SLOW?

Hexperience · Post by **Hexperience** » Mon Sep 14, 2015 1:47 pm

Is there somewhere I can find how to use slow? It doesn't work at all as I would expect. I have a mix that works fine, when I hold the momentary switch on my Taranis, channel 6 goes to +60 and returns to where it was when released. Super easy. Now I want to do the same thing, but just have it slower... I can't get my head around how it works. I know there's a bunch of virtual channels and curves etc...

Thanks in advance...

Post by **MikeB** » Mon Sep 14, 2015 2:31 pm

Slow applies only to a single mix, and is applied to changes to the mix source only.
Now, the mix you describe, what is the source?
If it is MAX, and you enable/disable the mix with a switch, then slow doesn't do much because the source is NOT changing (MAX is a constant).
What you would need to do is use SH as the source, and adjust the movement using weight and offset, something like:
+30% SH Offset(100%) Slow(U2:D2).

Mike.

Hexperience · Post by **Hexperience** » Mon Sep 14, 2015 3:08 pm

Thanks Mike, for the reply.

"Slow applies only to a single mix, and is applied to changes to the mix source only."

There is more in that sentence than my brain can process...

So what I'm trying to do is: Lets call it throttle on channel 6 (straight line curve)
Press switch H and the throttle channel goes slowly to +60 no matter where the stick currently is.

What I can't get my head around is what the source of the mix is... (and why) I'm not getting the basic logic.

ps. OpenTX latest sable version on Taranis plus.

Post by **MikeB** » Mon Sep 14, 2015 4:19 pm

You have a number of mixes available (64?) and you put 1, or more, on a single channel.
You edit each mix separately, and when you do, one of the entries is "source". This is the source of the mix.
I'm not up to date with openTx specifically, I develop and use ersky9x, but the principles are the same.
So you might have the following 2 mixes on a channel:
+100% Thr -- Source is Thr stick
R +60% MAX Switch(SH) -- Replace mix, Source is MAX

So with SH off, the first mix is active and you have normal throttle control.
When SH is ON, the second mix replaces the first, and the result is +60%.

Now, If I understand correctly, this is something like what you want, except when you switch SH ON, the output moves slowly to the +60% position, but when the switch is OFF, the throttle stick has normal control and nothing is slowed.

If this is what you want, it is going to be difficult to achieve.

Mike.

Hexperience · Post by **Hexperience** » Mon Sep 14, 2015 4:27 pm

Thanks Mike... yes, I have everything working just like you said, right up until I wanted to have the channel move slowly rather than instantly changing the throttle.

"If this is what you want, it is going to be difficult to achieve." <-- Thank goodness... I thought I was going crazy.

It seemed so straight forward at first. I had the mix doing what I want, even the delay was working perfectly. I thought that slow should work and in fact it does work the first time (edit: not every first time, maybe only after boot?). Any change after that and slow does not work.

Post by **MikeB** » Mon Sep 14, 2015 4:50 pm

I believe some success has been achieved doing this by using flight modes and fading from one to another. The fade applies a slow operation between the current output position and the new output position.

Mike.

Hexperience · Post by **Hexperience** » Mon Sep 14, 2015 5:14 pm

Darn... I didn't want to get into all that.... oh well. I'll give ersky9x a try on the taranis.

\\edit...
Hmm.. ersky does the same kind of thing on slow. It works the first time only. I know I'm missing something, but to me slow should be a little bit easier to use. Like I said, I have the mix working correctly, delay functions as it should, but slow is way too complicated for me to figure out. Because the slow setting is right there in the mix, it seems intuitive that slow would work like delay. (Again, I know it's probably a simple solution that I just can't get my head around). ER9X and OpenTX are fantastic and I'll keep reading to see what I'm missing.

Cheers

Post by **Kilrah** » Mon Sep 14, 2015 6:10 pm

On OpenTX you would simply add a line to your throttle control on the Inputs page. This is where you should do it as what you want to do is the switch basically to become a new throttle control, and as that's processed before the mixer your slow will work perfectly.

So just a 60% MAX line above the normal one with the switch you want to activate it.

Post by **MikeB** » Mon Sep 14, 2015 6:30 pm

The current value of every mix line stored internally. When a model is first loaded, the initial value of every mix is 0.
So, for a mix like:
+60% MAX Switch(SH)
As long as switch SH is OFF, it remains at the initial value of 0. When you switch SH on, the value changes to the 60% of MAX, changing slowly if there is a slow value set. If you now turn switch SH off, it just disables processing of the mix, but the value doesn't change anymore and stays at +60%. This is why you get a slow movement the first time you switch SH on, but not afterwards.
Remember also that slow only applies to this mix, not all the mixes on the channel.

OK, I've got the solution, using the fade principle. This is in openTx, but works in ersky9x as well.
+100% Thr
* 50% SH Weight(-50%) Slow(u1:d0) -- MULTIPLY multiplex
* -50% SH Offset(50%) Slow(u1:d0) -- MULTIPLY multiplex
+30% SH Offset(30%) Slow(u1:d0)

The first mix is your throttle.
The second mix scales this slowly down to 0% when you turn SH on. The mix goes from 100% to 0% over 1 second.
The third mix adds in your required 60%, again slowly over 1 second.

Kilrah: Does that work? The slow should not apply to the normal throttle movement when that is active.

Mike.

Post by **Kilrah** » Mon Sep 14, 2015 7:07 pm

Ah yep, missed that.

Hexperience · Post by **Hexperience** » Mon Sep 14, 2015 9:35 pm

Like this?

CH01
[I1]Rud Weight(+100%)
CH02
[I2]Ele Weight(+100%)
CH03
[I3]Thr Weight(+100%)
*= SH Weight(-50%) Switch(SH↓) Slow((u3:d0)
:= SH Weight(+30%) Offset(30%) Slow((u3:d0)
CH04
[I4]Ail Weight(+100%)

The throttle channel doesn't move at all with H off.
--- edit ----

missed the switch on the 3rd mix. When I have H off, I only have 50% of my throttle channel movement....

Post by **MikeB** » Mon Sep 14, 2015 10:31 pm

Oops, missed out the offset on the 2nd mix, I've edited the post above to put it in.

Mike.

Hexperience · Post by **Hexperience** » Tue Sep 15, 2015 9:35 am

Thanks again Mike. It's still a bit wonky but I'll play around with it.

Post by **MikeB** » Tue Sep 15, 2015 9:44 am

What version of openTx are you using? The implementation of OFFSET changed at some point. It used to be applied BEFORE the weight but now is applied AFTER.
If you put this mix on a channel by itself:
-50% SH Offset(50%)
it should go between 100 and 0 % as you switch SH.

Mike.

Hexperience · Post by **Hexperience** » Tue Sep 15, 2015 2:14 pm

2.1.3
It seems like when I do the multiply line it reduces the throttle channel, (with no switch on) to -50 to + 50. Weird...

If I change the multiply line to replace it works normally when no switch is on. I assume then that multiply is active all the time and not effected by a switch. (?)

So with the second line as replace, the slow movement to +60 is almost working. However, it always starts at +30 and slowly moves to +60 even if the throttle is at say -40

Post by **MikeB** » Tue Sep 15, 2015 2:45 pm

Move the 'multiply' mix to another channel (or copy it there), and change it to a normal add mix.
Check this channel is 100% with the switch in one position and 0% when in the other.
Normally, when using a switch as source, the output goes from 100% to -100%, a total of 200% change. This is why we use a weight of 50%, so it goes from 50% to -50%. By then adding in 50% offset, this changes to 100% to 0%.
This is what you are multiplying by, so 100% leaves the previous mix unchanged, and 0% turns the previous mix off. By having slow on the multiply mix, this steadily reduces the effect of the previous mix from full to nothing. Make sure you have the 50% offset included.
It worked fine for me when I tested it in companion.

Mike.

Hexperience · Post by **Hexperience** » Tue Sep 15, 2015 7:06 pm

Thanks very much Mike... I'm so sorry, but I've lost track of the mixes. Could I trouble you to post the lines again or an eepe file? Thanks very much sorry for not understanding....

Ps. I know your super busy and I really appreciate your help on this minor thing.

Hexperience · Post by **Hexperience** » Tue Sep 15, 2015 9:13 pm

Is there anything I can do to essentially set switch H back to 0? OR use a logical switch of some kind as the source?

Hexperience · Post by **Hexperience** » Tue Sep 15, 2015 11:25 pm

Does anyone have a working example of the slow function on 2.1.3? Thanks.

Hexperience · Post by **Hexperience** » Wed Sep 16, 2015 1:46 am

Flight mode fade in and out almost works but the delay doesn't work.

All I want to do is this, but have slow work....

Code: Select all

CH01 
    [I1]Rud Weight(+100%)
CH02 
    [I2]Ele Weight(+100%)
CH03 
    [I3]Thr Weight(+100%)
 := SH Weight(+60%) Switch(SH↓) Delay(u1:d0) Slow((u2:d0)
CH04 
    [I4]Ail Weight(+100%)

Post by **MikeB** » Thu Sep 17, 2015 10:16 pm

The mixes I suggested are in Model1 of the attached .eepe file. I saved this from companion 2.0.15.

Mike.

Hexperience · Post by **Hexperience** » Fri Sep 18, 2015 2:15 am

You are the best! Thanks so much for your time. I'll try it out first thing in the morning.

Hexperience · Post by **Hexperience** » Fri Sep 18, 2015 1:40 pm

Works perfectly. Thank you again. I almost had that at one point when I was following your suggestions, but I had the Switch setting as switch H down. I didn't realize that the source itself was all that was needed.

I consider myself a fair intelligent person, (don't ask my 15 year old son though) but the slow function is not as straight forward as it seems. I'm a visual person and if I ever figure it out I'll do a flow chart of how it works to help others (and myself).

OR if there is a logic diagram already of how slow functions please let us know where it is.

Again, Mike, thank you. Your patience and helpfulness know no bounds.

Post by **MikeB** » Fri Sep 18, 2015 4:03 pm

Perhaps if I now say again, slow ONLY applies to changes in the source and ONLY applies to the single mix, it might help your understanding.

Mike.

ReSt · Post by **ReSt** » Sat Sep 19, 2015 8:44 am

I tried to find a solution in another way using an auxilliary channel, a GVAR and finally two logic switches.

I found that slow up and slow down in one single mix does not work at all (doesn't give slow in any direction)

So I had to use one mixerline for slow up and one for slow down.

In the aux channel I used the GVAR as weight, and in the logic switches the GVAR was used to compare the position of the stick with the throttle channel position (to decide which mixline (slow up or slow down) had to be activated.

This did not work as expected.

The problem:
===========

In the logic switches, to work for the full range of the throttle channel value (+-100) the GVAR needs a range of +-1000
But in the mixer, you need the range of +-100

To work properly, in this case the mixer should use only 1/10 of the GVAR value

Reinhard

openrcforums

OpenTX example of SLOW?

OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?

Re: OpenTX example of SLOW?