Aha, ok thanks. You basically have to wait for a “multi press detection timeout” before the next press. I have multiple off press detection, but as being a reverse clicky guy it would be fairly annoying to have to wait between off presses with a 4 to 5 mode light. Out of curiosity, do you know exactly how long the timeout is on H17f or guppy3drv? I’ve set mine to half a second.
With H17f and possible guppy3drv there is no waiting on the off presses to change modes. IF you do wait you will either go back to mode memory, or reset to beginning of mode sequence.
Edit, removed video link. Wasn’t working
Sorry, but now I’m confused… you wrote “Leave on just a little bit longer before release”. This means waiting a little bit. Now you write there is no waiting 
That youtube link just brings me to youtube.com, not an actual video… I used search function though, I found a few to look at.
Reverse clicky— there is no waiting while off to change modes. Very brief off presses with cycle through the modes.
With a forward clicky, you have wait just a bit when you first press—let the light know its on in low before you release/press to switch to med. If you press-release/press to fast on H17f (possible guppy3drv). It will read inputs as double tap and go to Turbo or what ever the double tap is.
The “some time” is time on.
Edit, I don’t know why video link is not working.
Search—- H17F driver run down with mistakes. 1 cut Chad.
That’s the wait I’m asking about. Do you know exactly how long that wait is? 1/4 second? 1/2 second? 3/4 second? 1 second?
I know. What I am asking is if anyone knows how long “some time” is.
Hi Mike!
I don’t have the light with me right now! Later today I will check how it behaves both with RC and FC switches and will tell you as now I have some doubts, specially when using FC clicky.
I’ll try to make a video with both kind of switches and will link it!
Cool, that would be awesome!
It is actually very short. Here is a crappy video with me using a knife for a forward clicky.
Nice to see progress. 
In the meantime…I’m out of the GAW. I intended to use it with White Flat in Emisar D1. This combination doesn’t work well. Now I don’t have a combination of host and LED where this driver would really shine…I waited a bit with retiring because I thought that maybe I’ll think about some good combo. Well, it didn’t happen.
Thanks anyway!
Hi again Mike!
So, I picked my Convoy S2+ with the guppy3drv and made a try with Forward Clicky switch and Reverse Clicky switch.
DRIVER: FET + 7135 Driver - 17mm - MTN-17DDm
FIRMWARE: guppy3drv Instructions
For what is worth, I am using mine in the configuration 10-5-5 (FF > 1 > 5 > 25 > Double for 100%) 4 modes + 100% and without memory activated, so it always starts in FireFly mode.
FC switch:
“Resumé”
a) from OFF, consecutive single half presses cycle through the different 4 levels always as momentary ON modes
b) releasing the switch within the cycling process implies that the it will restart in Firefly mode the next time I half press/click the switch
c) the double half press for Turbo (100%) is active independently of the momentary mode I am in, so I can go Turbo whenever I want
d) HOWEVER, when I am on the modes FF, 1 or 5, if I double click for turbo and after turbo I do a quick release>press again, the light will get back to the last momentary mode used
e) on the mode 25 (4th regular level), if I double click for turbo and then do the “quick release>press again”, the light will restart in the FF mode, not the 25 mode.
f) obviously, a full click at any time “locks” the mode I am in at the moment, so I can only do the double click for turbo when doing half presses. Then I can lock Turbo by doing a full press.
——/////——
RC switch:
“Resumé”
a) full click turn the light ON in FF mode; another full click turns the light OFF
b) fast full clicks for ON/OFF don’t get me into Turbo; the light only switches ON in the next output level/mode
c) when ON, single half presses cycle through the different 4 levels as “locked” modes
d) when ON, from any mode, a double press takes me to Turbo (100%), so I can go Turbo whenever I want
e) HOWEVER, similarly to what happens to FC switch, when I am on the modes FF, 1 or 5, if I double click for turbo and after turbo I half press/tap the switch, the light will get back to the last mode used
f) on the mode 25 (4th regular level), if I double click for turbo and then tap the switch, the light will restart in the FF mode, not the 25 mode.
Please apologize as I made mistake before the level 25 (4th) so I’ve restarted from there again.
This is curious, I had never tried this, but despite the switches used, they will behave similarly. All and all, in the 4th level, it doesn’t get back to it after Turbo, it will always go for FF.
I must mention that I didn’t use lighted switches, as they may have influence in the driver behaviour.
I hope this was useful and gives you some input on this UI! 
As I mentioned, please be aware of the configuration I am using (10-5-5) and no memory.
Thanks for those videos! And chadvone too.
It makes sense expect for one thing regarding FC (e) , RC (f) and your comment: “All and all, in the 4th level, it doesn’t get back to it after Turbo, it will always go for FF.”
I find it a little odd that the behavior is different on the 4th level mode. Is this by design and something you appreciate, or would you rather have it go back to 4th regular level after quick tap from turbo?
Also a question about timing, using RC video for reference. At about 0:07 to 0:16 you do regular mode switching. Then at 0:17 you do double tap for turbo. Is it specified anywhere what the time limit between presses is? Obviously if you do two presses directly after each other with for example 0.1 second interval the light will switch to turbo, but if you do two presses with two second interval the light just switches mode after each press. What is the time limit where two presses are either identified as double tab for turbo or identified as two simple mode switch presses? I think this is the critical part weather my UI will work for you or not. The rest is easy, I support most of it as it is already, but the timing between presses is something that one gets used to. If it’s wrong on another driver it just gets annoying.
Thanks Mike! Well, all that is happening is by design, meaning that I didn’t program anything in the driver. This is a DrJones firmware in a MTN Electronics driver. I only noticed that “odd” situation when I tested it last friday with both types of clicky switches.
For my taste, I would rather have it to go back to the 4th level, instead going to FF after turbo. I’d find it more consistent and standardized!
However, I think this is a thing that also happens in some other flashlights (ex: Olight M2R Warrior, where after Turbo, a press&hold takes us to Low mode instead of the last used mode).
I didn’t find any specification about that time limit in the pages where I saw the UI :zipper_mouth_face: Normally it juts says “double tap”.
Yup, that is correct. I cannot measure that accurately, but a longer interval between presses will switch mode.
Still, there is a time interval in which we can double tap to turbo, so it may be slightly bigger than 0.1s. Meaning that sometimes I take bit longer to do the second press and it will still lead me to turbo.
If I can, tonight I may try to do a video exemplifying those small differences.
I’ll try to show this on the video, so that you can make a more “appropriate guess” or a rough estimation of the time needed for those presses.
You prefer the demonstration with RC or FC or both, Mike?
I know you didn’t program it, but by design I mean if it’s intentional. To me it looks more like an unintentional feature, in other words a bug. But I guess Dr Jones is the only one who can really answer that. In either case it doesn’t make sense to me so I won’t implement it. My firmware switches back to last used mode regardless of which mode that is.
I only need to see one, and which one is not important so what ever is easiest for you. I’ll take a stab at guessing it’s half a second, meaning two taps with on time between taps under half a second will register as double tap (turbo), and two taps with over half a second on time between taps will just do regular mode switch.
Oh, sorry, I didn’t understand it well at first!! :person_facepalming: Yup, seems like “bug” as it doesn’t make many sense to jump to FF after turbo on that level.
Anyway, like you say, it doesn’t make much sense to me either. But, as I normally use it with the FC switch, I don’t tend to go to the 4th level and to turbo from there. If I used it with RC switch, I’m sure I would bother more about that, as I like to return to the previous used mode.
Ok then! I will try it in a way to demonstrate those periods more or less accurately! I’ll try the different timing solutions also to check the excess of delay when pressing! I’ll post them tonight :+1:
Another thing worth mentioning… I also see that guppy3drv doesn’t appear to support short or long off taps. It’s either a tap under half a second, or a “cold start” if the the light is off longer than half a second.
I already have a UI in my firmware with the same behavior as you are looking for, but with one exception. Instead of double tap for turbo it’s a single long tap. My firmware has short tap (1/4 second or quicker), and long tap (over 1/4 second to 1 second). Cold start is if the light has been off for more than one second. So short off tap to cycle modes (excluding turbo), and long tap for turbo. Short or long tap from turbo goes back to last used mode. Would this be of interest or do you think you would still prefer double tap?
Although I have “traditional” mode UIs in my firmware I personally don’t use them anymore, at least not with my clicky lights. I use an UI with two modes, normal and turbo. Short tap alternates between the two, long tap in normal mode enables ramping. When ramping is enabled it’s short tap to ramp up, long tap to ramp down. Tap again to stop ramping. After a timeout of no button activity it switches back to initial state.
Anyhow, all these UIs are in the firmware, changing UIs is some what similar to guppy3drv mode group changing. I don’t have pre defined mode groups like guppr3drv. I have a setting for mode count and the possibility to adjust each mode by ramping.
I would like to see double tap to TURBO and a double tap to return to last mode.
And a single tap to resume level changes.
Double tap in , Double tap out.
Hey Mike, here are the videos I made a while ago:
Forward Clicky Switch
Reverse Clicky Switch
Well, while I was trying the light with the Reverse Clicky Switch, I noticed it has a longer press to return to FF mode.
So, lets say I’m on levels 2 or 3 and with double tap I go to Turbo. If in Turbo I do a tap, I’ll return to mode 2 or 3; however, if I press the switch a little longer, I will return to FF mode.
So it supports this, at least in this Mode configuration (10-5-5). I never tried it with other configs :zipper_mouth_face:
I will answer based on my preferences so far, that normally imply having a short shortcut to turbo, like on this light. I’m afraid that a longer tap/press will take the quick access to turbo from OFF, using a FC switch. But, honestly, I guess never tried that kind of option. Would it work well on the FC (like: long tap & maintain press or fully click, to lock the mode) or it will be better on the RC (long tap & release to maintain the Turbo locked)?
One thing I do like is that it goes back to the last used mode, in all modes!!
Hum, I only used ramping on a RC when I used Crescendo FW, by Toykeeper a while ago. I stopped using it cause I didn’t control the ramping as in the UI: it started going up or down by itself and then there are taps to stop or restart, or to take back to lowest or highest levels.
I guess if they are in the FW already it can be interesting to try the different possibilities Being user configurable is a nice option to have, as different needs may imply different UIs! :sunglasses:
I can do that, it’s just a matter of timing for double tap detection. But, what would a single tap in turbo do?
Thanks! I’m looking at them with frame by frame stepping (I downloaded them). I should be able to get a time limit from them.
That’s what got my started down this road. I have different preferences for different situations, as it is now I have 5 different UIs in my firmware… well, actually it’s 15 because they behave differently depending on switch configuration (E-switch, clicky or dual switch). A few more UIs are coming based in several suggestions in here. It’s great having 16KB to play with, I can have a lot of options without having to go byte hunting for every single addition.
I made a short video of my UI #3 off switch ramping. First I’m short tapping to switch between normal and boost a couple of times. Then I do a long tape which enables ramping (some flashing indicates ramping active). Then I short tap to ramp up, long tap to ramp down. Then I leave it inactive for two seconds and ramping times out (short flash indicates and the mode level is written to memory), and then it’s back to switching between normal and boost with short taps…. until a long press for ramp activation.
Turbo is not “rampable”. Both long and short tap in turbo switches to normal mode.
I use very low mode levels for demonstration so I don’t blind out the camera, and I’m only ramping minimal amount, the full range takes longer.
Single tap for this, long press for that, NarsimMLSXXX, CrapduriXXX…
I'll tell you something Mike C, STFU'em all and make it as you like LoL. :-D 
Suggestion: Lo/Hi/Strobe (heading for my nice cup :-D of STFU now)
Cheers 