- Posts: 271
Feature proposal: Add option "sticky" to safety sw
- linux-user
- Topic Author
- Offline
Less
More
05 Jan 2014 14:23 #17983
by linux-user
Feature proposal: Add option "sticky" to safety sw was created by linux-user
Hi to all, and thanks for the amazing firmware.
@PB: if you ever decide to accept donations let me know.
I know, it's possible to implement a "sticky throttlehold" with virtchannel like this:
=============
[channel3]
safetysw=Virt2
safetyval=-100
[virtchan2]
template=complex
[mixer]
src=Virt2
dest=Virt2
usetrim=0
curvetype=min/max
points=0
[mixer]
src=Ch3
dest=Virt2
offset=-1
usetrim=0
muxtype=add
[mixer]
src=AIL
dest=Virt2
switch=HOLD1
usetrim=0
curvetype=fixed
================
Now I am thinking if it would be possible to implement that feature in deviation itself,
which would make it easier for the user to config.
The logic would be simple:
after safetysw has been flipped and switched back to normal.
- keep the channeloutput at safetyval until the result of all applied mixers = safetyval
There could be a new option like this:
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes
What do you think?
@PB: if you ever decide to accept donations let me know.
I know, it's possible to implement a "sticky throttlehold" with virtchannel like this:
=============
[channel3]
safetysw=Virt2
safetyval=-100
[virtchan2]
template=complex
[mixer]
src=Virt2
dest=Virt2
usetrim=0
curvetype=min/max
points=0
[mixer]
src=Ch3
dest=Virt2
offset=-1
usetrim=0
muxtype=add
[mixer]
src=AIL
dest=Virt2
switch=HOLD1
usetrim=0
curvetype=fixed
================
Now I am thinking if it would be possible to implement that feature in deviation itself,
which would make it easier for the user to config.
The logic would be simple:
after safetysw has been flipped and switched back to normal.
- keep the channeloutput at safetyval until the result of all applied mixers = safetyval
There could be a new option like this:
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes
What do you think?
Please Log in or Create an account to join the conversation.
- FDR
- Offline
05 Jan 2014 14:34 #17985
by FDR
Replied by FDR on topic Feature proposal: Add option "sticky" to safety sw
I wouldn't like it to work that way.
Please Log in or Create an account to join the conversation.
- RandMental
- Offline
Less
More
- Posts: 521
05 Jan 2014 14:42 #17986
by RandMental
Replied by RandMental on topic Feature proposal: Add option "sticky" to safety sw
I agree with FDR, I have Sticky TH on some smaller models, but for larger 600+ Helis en especially Nitro driven helis and planes you have a few engine cut options, ie. Cut to idle and Kill the engine.
I believe the current flexibility allows one to implement all these variants with relative ease.
I believe the current flexibility allows one to implement all these variants with relative ease.
Please Log in or Create an account to join the conversation.
- linux-user
- Topic Author
- Offline
Less
More
- Posts: 271
05 Jan 2014 15:18 #17988
by linux-user
Replied by linux-user on topic Feature proposal: Add option "sticky" to safety sw
Ok, there are situations where you don't want "sticky TH"
That`s why I proposed it as an option, where you can have either:
====================
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes
==== or as it is now =====
[channel3]
safetysw=RUD DR1
safetyval=-100
==========================
So it's still the user who decides which behavior he wants.
The only downside I can see is the risc of introducing bugs,
besides the development effort that might not be worth it.
That`s why I proposed it as an option, where you can have either:
====================
[channel3]
safetysw=RUD DR1
safetyval=-100
safetysticky=yes
==== or as it is now =====
[channel3]
safetysw=RUD DR1
safetyval=-100
==========================
So it's still the user who decides which behavior he wants.
The only downside I can see is the risc of introducing bugs,
besides the development effort that might not be worth it.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
Less
More
- Posts: 4402
05 Jan 2014 16:12 #17991
by PhracturedBlue
Replied by PhracturedBlue on topic Feature proposal: Add option "sticky" to safety sw
currently Deviation does not keep track of historical state, but you are right that it would be easy to implement in Deviation. As was brought up in another thread, the main problem with using a safety switch is that you cannot take the final output as an input to another mixer.
I don't have much opinion one way or another.
I don't have much opinion one way or another.
Please Log in or Create an account to join the conversation.
Time to create page: 0.038 seconds
- Home
- Forum
- Development
- Development
- Feature proposal: Add option "sticky" to safety sw