Sticky T-Cut Throttle
Sticky T-Cut Throttle
I am trying to set up the throttle, so that it has a fail safe. It is easy to do in a simple way by programming up a switch to replace the value set by the throttle, and in doing so deactivate the stick.
What I am looking for is some mix where on switching the stick back on, that you have to set the stick to zero before it becomes active again. This will make it doubly safe if the throttle is on some other setting other than zero and the switch is turned off, which would normally mean that the motor would instantly go to what the throttle setting is.
Hope that makes sense.
What I am looking for is some mix where on switching the stick back on, that you have to set the stick to zero before it becomes active again. This will make it doubly safe if the throttle is on some other setting other than zero and the switch is turned off, which would normally mean that the motor would instantly go to what the throttle setting is.
Hope that makes sense.
Re: Mixology
Use the "Sticky T-cut" template in eePe. That's what it does.
Ted
Ted
Re: Mixology
I'm afraid that the information you have given me is meaningless. I don't have any templates in the version I have loaded onto my transmitter. I did look around to see if anyone had posted a mix, and I came up empty on that. Hence why I am asking here for some help or a pointer to it.G550Ted wrote:Use the "Sticky T-cut" template in eePe. That's what it does. Ted
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: Mixology
Ted did say look in eepe for the template, not er9x. The templates are always available on eepe even if you have loaded a NO-TEMPLATE version of er9x.
Mike.
Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: Mixology
For an explanation of how it works along with an eepe file to use as an example look here.
http://er9x.googlecode.com/svn/trunk/do ... amples.zip
It is under Throttle Hold and is the 3rd example. There are 4 total examples of a throttle hold and each one is on a separate channel.
http://er9x.googlecode.com/svn/trunk/do ... amples.zip
It is under Throttle Hold and is the 3rd example. There are 4 total examples of a throttle hold and each one is on a separate channel.
Re: Mixology
Now it makes sense. Thanks guys. You are all stars.
- Scott Page
- Posts: 864
- Joined: Wed Dec 28, 2011 3:32 am
- Country: United States
- Location: Tri-Cities, Washington State
Re: Mixology
EDIT** brain fade. sorry
Last edited by Scott Page on Wed Dec 28, 2011 7:18 am, edited 1 time in total.
-
- Posts: 11
- Joined: Fri Dec 30, 2011 12:19 pm
- Country: -
Re: Sticky T-Cut Throttle
Just a quick question which is kind of related to the original post about throttle cut.
Do you think it would be possible to set a throttle cut to go to a specified amount of throttle but using the sprung loaded trainer switch where once the switch is flicked the throttle is cut and it stays that way until the trainer switch is flicked again? I am trying to get it to work right now and I am missing something in my brain to understand it fully lol
Do you think it would be possible to set a throttle cut to go to a specified amount of throttle but using the sprung loaded trainer switch where once the switch is flicked the throttle is cut and it stays that way until the trainer switch is flicked again? I am trying to get it to work right now and I am missing something in my brain to understand it fully lol
- wheelspinner20
- Posts: 175
- Joined: Tue Dec 27, 2011 6:22 pm
- Country: -
- Location: Michigan, U.S.
Re: Sticky T-Cut Throttle
Trainer is just a momentary. So the controller chip only acts on its real time position... either open or shorted. I think this would be tricky.
Are you out of switches? whats the specific application, this might help the experts to come up with a happy medium!
Pat
Are you out of switches? whats the specific application, this might help the experts to come up with a happy medium!
Pat
no more quippy little latin phrases.! Its old
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: Sticky T-Cut Throttle
It may be possible, it will use a lot of custom switches. However, I'm not sure it's a good idea, as you can't guarantee which way (cut or not cut) it starts in, and no obvious indication which way it currently is. Please detail your requirement fully.papa_lazerous wrote:Do you think it would be possible to set a throttle cut to go to a specified amount of throttle but using the sprung loaded trainer switch where once the switch is flicked the throttle is cut and it stays that way until the trainer switch is flicked again? I am trying to get it to work right now and I am missing something in my brain to understand it fully lol
Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: Sticky T-Cut Throttle
Somewhat old but interesting topic, here is a new idea.
The EEPE example 3 has a solution using 2 custom switches and 5 mixes (!).
This is fine if you have plenty of mixes available, but if you're mix bound and not switch bound, any mixing freed up is helpful.
Here's an idea to get sticky throttle cut using only the one basic throttle mix (freeing 4 mixes with respect to initial example), a safety switch and 3 custom switches, only one more than the original example.
Explaination:
SWC is triggered when the THR stick is < -95.
SWA and SWB act as the memory of (THR stick < -95 and THR switch on):
SWB is triggered if THR stick is < -95 OR if (THR stick < -95 and THR switch on) was previously observed (SWA).
SWA is triggered if the THR switch is on AND if SWB is ON (bootstrapped in particular when THR stick < -95). SWA goes OFF as soon as THR switch is OFF, so should SWB.
I don't see why this wouldn't work but I'm getting strange results under eepe (v347): when I start eepe fresh it works at advertised, but sometimes after several modifications and simulator runs, it seems buggy as the switches A and B seem to go ON when I flick THR ON (and erratically go ON/OFF without any user intervention), even though the throttle is not at idle position. I don't see a good reason for this. I'm trying to figure out if my logic is flawed and incomatible with the eepe/er9x switch evaluation process, or if this is an eepe bug.
Any idea? Anybody want to test this?
The EEPE example 3 has a solution using 2 custom switches and 5 mixes (!).
This is fine if you have plenty of mixes available, but if you're mix bound and not switch bound, any mixing freed up is helpful.
Here's an idea to get sticky throttle cut using only the one basic throttle mix (freeing 4 mixes with respect to initial example), a safety switch and 3 custom switches, only one more than the original example.
- Set your throttle channel to 100% THR
- Set your custom switches as follows:
- CswitchA:AND THR SWB
- CswitchB: OR SWA SWC
- CswitchC: v<ofs THR -95
- set throttle channel safety switch to : !SWA -100
Explaination:
SWC is triggered when the THR stick is < -95.
SWA and SWB act as the memory of (THR stick < -95 and THR switch on):
SWB is triggered if THR stick is < -95 OR if (THR stick < -95 and THR switch on) was previously observed (SWA).
SWA is triggered if the THR switch is on AND if SWB is ON (bootstrapped in particular when THR stick < -95). SWA goes OFF as soon as THR switch is OFF, so should SWB.
I don't see why this wouldn't work but I'm getting strange results under eepe (v347): when I start eepe fresh it works at advertised, but sometimes after several modifications and simulator runs, it seems buggy as the switches A and B seem to go ON when I flick THR ON (and erratically go ON/OFF without any user intervention), even though the throttle is not at idle position. I don't see a good reason for this. I'm trying to figure out if my logic is flawed and incomatible with the eepe/er9x switch evaluation process, or if this is an eepe bug.
Any idea? Anybody want to test this?