Driver giveaway: Constant current 17mm drivers, winners (finally) announced, post #2.

Isn’t the construction of D1 and D4 similar regarding the driver part?
If yes, a double sided driver can be used, I did this in my D4 RGBW mod, see link below.
But the stock driver is 22 mm in diameter.

Just a question to anyone and everyone who likes moon mode with a “traditional” mode up/down interface. Is it preferred to have moon mode only accessible with a shortcut? If so, what shortcut? I’d like to know for both E-switch and off-switch/clicky lights. Or do people prefer to have moon mode in the regular mode cycle?

I have 2 different perceptions on this, through the use of different lights:
a) using the S2+ with guppy3drv FW + forward clicky switch (that I mentioned before), I do like having moonlight on the regular cycle mode as I can have a momentary ON by half pressing the tail of the flashlight (with memory turned OFF, if I release the switch it always starts on ML);

b) in another situation, using the Olight S1R Baton or the Olight M2R Warrior, both have the option to access moonlight from a long click&hold when OFF. When advancing the modes (ML > L > M….) , the ML is no longer on the way unless you switch the light OFF and then do the click & hold again.

I find both situations very useful although very different, once on the first we have a momentary clicky switch (the way I use it: 3 or 4 modes + turbo with double click, with ML on the regular cycle) and on the second an e-switch (ML only accessible from click & hold from OFF and then out of the regular cycle).

If I had to chose, I guess a shortcut from OFF to ML is always a good thing to have, with the possibility to advance further on the modes and then letting ML out of the cycle (as Olight does). But always with the possibility to access ML from OFF.

Also, Emisar D4 , with ramping IOS, has that possibility, to click & hold from OFF and starting to ramp from the lowest level.

In my opinion, that is a nice feature to have, as a configurable memory (so that we can set the light to start on the lowest, highest or last used mode) :wink:

This exactly. I like the click-hold from off shortcut to Moonlight and thereafter normal modes (without Moonlight in the cycle). It would also be great if it were possible to go two directions through modes, especially in cases of more than four modes being available. In that scenario, being able to hit Moonlight by cycling backwards into it would also be nice.

Click hold for moonlight is good then forward cycle low medium high. Alternative moon on then L/M1/M2 in cycle double click to high. Keep the blinkies or add another cycle mode three clicks from moon for blinky modes only. (slim4)

My favourite is starting ML and going up, with direct shortcut to moon.
I also find it useful to have direct shortcuts to:

  • turbo
  • maximum thermally sustainable mode

I guess the last one could simply be a configurable “favourite mode”.

Thanks for the input! I’ve always had click and hold from off (E-switch) starts setup menu selection and hidden modes. I can easily change that to double click and hold on second from off.

In my “traditional” mode up/down interface for E-switch lights I go in both directions. Click and keep holding cycles up and stops on highest mode/boost. Double click and hold on second cycles down and stops on lowest mode. Wrap around is only enabled if mode change is initiated from one of the ends, like mode up from boost or mode down from lowest mode.

For clicky switch lights I have short off press for mode up, long off press for mode down.

I will implement a few settings for moonlight options. Menu settings and changing options is more challenging for clicky switch lights, in particular forward clicky. In these cases I think setting up the light as desired during flash faze is essential, even though menu options will still be available.

Exciting drivers Mike C. Thanks for the opportunity. The SLIM-4 most interests me. The high-side regulation would make it these great for emitters with cathode connected thermal pads and lights with no thermal pad.

My favorite UI (with a momentary switch) would do the following:

From Off:
1 Click - On with last used mode memory
2 Clicks - Highest Mode
3 Clicks - Strobe (dual frequency like NarsilM, but not that super fast high frequency it has)
Medium Length Hold - Moonlight Mode
Long Hold - Lockout with no out other than disconnecting power

From On:
1 Click - Change output level
2 Clicks - Highest Mode
3 Clicks - Strobe
Medium Length Hold - Off

——Option 1————————————————————————————————-
Thanks for the giveaway.
When it comes to UI my preferences are modes:
2 switches, one mechanical only for power on/off and second electronic switch for mode operation.
3 modes in total, about 20, 50 and 100, no moonlight/firefly, no strobe, sos, only blinking mode I would accept would be bike mode (and it’s not actually blinky, more like pulsating, 60 constant output with occasional (every second or third second) short “spike” to 100%. But this has to be “hidden” mode.
It remembers mode you used when powering off regardless how long you used it for.
Low battery warning at about 3.2-3V, power off at about 2.7-2.8V
Small red led around the e-switch to indicate low battery.

——Option 2————————————————————————————————-
There is an alternative for mechanical switch + e-switch lights.
I call it “How Crelant should have made their UI” UI :smiley:
Mechanical switch only turns light on and off in last used mode, does not change mode
E-switch only changes modes,
short click to advance to next mode (mode 1, mode 2, mode 3 -> mode 1, mode 2…. and so on)
fast double click to go to turbo,
press and hold to adjust the current mode slot,
3 or 4 slots for modes,
you select a wanted mode slot with short clicking, then press and hold to adjust output level, light will ramp up thru 10 or 12 intensity levels, when it gets to max you get 2 short blinks so you would know “this is the max”, if you keep holding e-switch you are going to min and ramping in steps starts again.
Basically you have 3 (or 4) memory slots to set modes as you wish, you can do something like: level 2, level 10, level 5, level 12 or 1-5-8-12 or 12-8-5-1 etc…
Memory is instant, it does not depend on time, if you click e-switch to use 3rd memorised level and then instantly turn off the flashlight with mechanical switch it will power on in 3rd memorised level.
Low battery warning at about 3.2-3V, power off at about 2.7-2.8V
Small red led around the e-switch to indicate low battery.

——Option 3————————————————————————————————-
More complex version would be for e-switch only lights.
Short click to turn it on in last used mode, also to advance to next mode,
Double fast click for instant turbo from off state or from any other mode,
Long (0,5 seconds or so) press from off for moonlingt mode
Long (0,5 seconds or so) press from any mode to turn it off.
4 modes, that includes moonlight and “turbo” + described hidden bike mode.
Low battery warning at about 3.2-3V, power off at about 2.7-2.8V
Small red led around the e-switch to indicate low battery.

that would be about it :smiley:

Nice drivers, here’s a new idea:

Maybe we can use an e-Compass to create a pretty unique UI. Click for on and off (with double click for turbo, and all the other fancy shortcuts), but then hold, and rotate the light to control brightness. Clockwise for more, counter-clockwise for less output. Something between 90°-120° from low to high could be great. Involves communication between MCU and magnet field sensor though.

People's too fond of super-low modes, they're handy for some situations. With regards to modes I prefer even spacing, up there I suggested 11.1% - 33.3% - 100% (by 3x each time), albeit for slightly less difference a smaller multiplier can also do: 16% - 40% - 100% (by 2.5x each time). Of course this is just my point of view, but please bear in mind whateverfold increases in driving current/power at the emitter do translate in lesserfold light output increases.

Cheers ^:)

Always great to see your work, Mike C, nice to have a chance to see what you have in the making.

I’m not in for the giveaway, for a reason you might understand more than anyone else: I don’t use what I can’t program myself :smiley:
And it would be a pity just to have such a great driver lying here, knowing that someone else might have use for it.

But I’m happy to chime in on your UI question.
I don’t want wrap around - ever. Which rules out about every stock clicky firmware in the repository…

1. clicky lights

- 2 to 7 modes, evenly spaced in brightness

- usually 4 mode groups: 7 modes, 6 modes w/o turbo (for muggles), 4 modes, 2 modes

- short press (tap): brighter mode

- medium press (1sec): darker mode

- no wrap-around = no accidental moon after turbo, no accidental turbo after moon (you know: wham! ugh! here goes my dark adaptation) and several short presses in a row always reliably result in highest mode

- 12 short presses to battcheck

  • 15 short presses to config mode (modegroup, memory, turbo timeout and LVP can be toggled)

2. momentary lights
a)
similar as the clicky UI (modegroups, battcheck, config mode) with

- no memory

- short press from off = moon

- long press from off = turbo

- long press from on (any mode) = off

- short press: brighter mode

- medium press (1sec): darker mode

- no wrap around
b)

- short press (tap): on/off with memory

  • hold when on: ramping up and down and up and down and…

Interesting idea, thinking out of the box, that’s for sure. I don’t think I would use it myself though, I mostly use my lights when moving underground and a simple UI with a few clicks will always be easier.

Oh yes, I understand completely! Be it a headlamp, bike light or hand held, if I can’t stick one of my own drivers in it I’ll either make a new driver for it or bin it :slight_smile:

I haven’t thought about it like that. It’s a good idea indeed, in particular for clicky lights. I’ll make a user setting for it. Thanks for that one.

This differs some what from most people. Almost everyone seems to prefer short press from any mode to be off, regardless of UI type. I used to prefer long for off myself but thought I was alone so I made some UIs with short off to see what the fuss was about. I had to put some effort into thinking about the other button sequences and ended up being converted myself, now I prefer short for off too. I did have multiple UI options for off selection in some older firmware, I might bring that back to life. In any case, it is refreshing to see other options than short for off. Apparently I wasn’t alone like I thought.

Thanks for the input!

Short press from any mode to OFF? WTF? And how the hell do you switch modes? Pretty ill-suited if long press or whatever, imho. :facepalm:

Cheers

Same here. After adapting my UI to short off I like this type more. And short off doesn’t confuse muggles if they get their hands on my lights.

Interesting, though it needs a tail switch. Otherwise locating the switch during the next use would be a problem
I love QTC twisties and this very much reminds me of one.
Among the things that QTC does well is the ability to fine tune the output easily. I’m afraid that preventing accidental output change during regular user movement could interfere with that. I’ve spent a while looking for solutions, I find nothing satisfactory.
So…I’m afraid it wouldn’t work as well as I wish it would, but I surely miss many implementation options and maybe I’m just exaggerating the impact of regular hand movements.

My Driver Setup For Single LED EDC

*Press and hold when OFF= Moonlight

*Single Click = ON

*Single Click = OFF

****Press And Hold When ON****RAAAMMMMMPIIIINNNNG!!! (I think that the way you setup these drivers the ramping would be super smooooth!!

*Double Click = 1st of 3 BRIGHT modes

*Double Click = 2nd of 3 BRIGHT modes

*Double Click = 3rd and BRIGHTEST mode

*Triple Click = Enters into mode 1 of 3 separate modes. (Bicycle Flashing Light)

-Single Click = 2 of 3 separate modes. (Battery Check 1 blink low * 5 blinks full *

-Single Click = 3 of 3 separate modes. (S.O.S.)

-Single Click = OFF

* When OFF, Double Click Then Press And Hold On 3rd Click = Lockout

* I REALLLY WANT ONE OF YOUR DRIVERS PLEEASE! I know Im new here but I really want to build a sweet Thrower with one of these drivers!!

A well defined set of proportionately scaled modes is a most standard configuration which can fit everyone. For a 2.5x order of magnitude and 5 modes total (4 plus moonlight) that would be, in percentage: 0.2, 6.4, 16, 40 and then 100% (2.5x-fold the previous mode driving current ensures at least doubling the light output). And bullshite anything else LoL! :-D

I noticed that no light serves my major use pattern well…
With e-switch lights I use physical lockout a lot. Light is on, I unscrew the tailcap to turn it off. When I want it back on I screw the tailcap back, find the button, turn the light on.

If the light turned on as soon as I screwed it back I could avoid the last 2 steps.

OTOH it would prevent using shortcut to moon and blast me and everyone around with whatever the default mode is.

I had literally 1 e-switch light where I didn’t use physical lockout. Not that it had one….but even if it did I wouldn’t have to.
Nitecore Tini. It has that annoyingly long click to turn on. I hated that. And it would turn on by itself from time to time anyway.
But maybe a more elaborate turn-on sequence would serve as well as a lockout? 2-click on?

I have lock out feature in my firmware, and with the ATtiny1634 I have the parasitic drain down to 1uA which is theoretically over 3000 years with a 3000mAh cell. I haven’t checked if the CN regulators leak any current yet though, but if they don’t there shouldn’t be a need for physical lockout.

I do detect weather power is back after cell replacing in E-switch only configuration. Currently I have it set to blink a confirmation that the cell is back, then the light goes back to sleep. I haven’t decided weather it would be better to just have the light turn on again, but just as you mention it could blast everyone around.

For the actual lockout I am considering multiple options. One full lockout that requires full unlock sequence, another partial lockout that requires simple sequence on each startup until full unlock is done. I had to have lockout on my BMF SRK because it almost started a fire in my backpack during a mine exploration, but it’s tedious to have to do full lock/unlock each time I take it out of the backpack for photo shoot (it’s off-switch light), so a semi-lock feature would really be helpful in these situations.