×

Notice

The forum is in read only mode.

Devo 7e - timers with throttle starting with -80

More
17 Jan 2018 00:40 #66918 by silverAG
For some of my whoop quads with silverware, I'm using throttle with offset so my starting point is not -100 but -80 - and I have problems with timers because they start to count when throttle goes from -99 to 0 and above - so timers counts even when my throttle stick is down at -80% and motors are off (motors on my whoops with silverware starts to spin at around -75).

Is there any way I can set timers to work on custom throttle value, like, for example, when throttle pass -75 and not -99?
More
20 Jan 2018 19:15 - 20 Jan 2018 19:16 #67021 by gdenton
Here's one way to do this:

Set the Timer Switch to a virtual channel.
Edit the virtual channel mixer:
set to Simple
Src = THR
Curve = 9 point
Point 1 = -100
Point 2 = -89
Leave Points 3 thru 9 at 0

This starts my timer @ -74% on a new model file (no trim/offset/throttle curve).
Last edit: 20 Jan 2018 19:16 by gdenton.
More
22 Jan 2018 08:42 #67038 by silverAG
I tried simmilar trick but I used complex mixer and different points. I'll try this - looks simple and OK.

Thanks!
More
22 Jan 2018 12:02 - 22 Jan 2018 12:04 #67040 by silverAG
Tried. It works fine! But not with sticky throttle hold :(

I tried to replace THR with Ch3 as source in Virtual channel because my sticky throttle hold value is -125 at Ch3 - and sticky throttle behaves as expected - when I move stick, Ch3 stays -125 (which is OK and as expected for sticky throttle) but timers are still counting as soon as throttle stick is moved... Of course, virtual channel is assigned to timers... :)

So I tried to use Ch3 instead THR as input in Virtual channel, but that does not help - looks like Ch3 when used as input in virtual channels still pass original throttle value, and not the one modified by "sticky hold" code.

Strange...
Last edit: 22 Jan 2018 12:04 by silverAG.
More
23 Jan 2018 02:52 #67056 by gdenton

silverAG wrote: looks like Ch3 when used as input in virtual channels still pass original throttle value, and not the one modified by "sticky hold" code.


You are right, and I don't think that's the way it should work.

Can one of the devs comment on this please?
Time to create page: 0.219 seconds
Powered by Kunena Forum