1. I am used to triple-click on e-switch lights. That just works for me.
2. Signaling battery level during use (drops to 50% - light blinks it out somehow) would be useful…but very confusing to unprepared users.
3. I tend to prefer 4-5 bettery levels to voltage readout.
Triple-click on E-switch was what I was thinking too.
Any suggestions on clicky? My old clicky firmware battery check can only be done from off so it doesn’t interfere with normal mode changing. How does it work in other clicky firmware/lights?
In Bistro (has capability to detect “long presses” via an OTC), you long-press from the lowest mode to get into the blinky modes including battery check.
In Biscotti, in some mode groups it’s just an option in the normal modes rotation.
In Babka (a firmware of mine), I hide it behind a triple-click.
Thanks for the info, I haven’t been looking at other firmware for ages. I’m not fond of the first two options, I guess I’ll go with my old method for clicky lights, a click sequence from off.
Was going to say this, but you did it 
I guess this would be a nicer option. That way a person wouldn’t need to do “things” when on just to check battery. I have some lights with Bistro (on different drivers and mode configuration) and I find that battery check more usable than the one in Biscotti (in which I would need to cycle through lots of modes to get there).
Still, even in Bistro, the need to long press from the first sequence mode is not as pleasant as clicking from OFF for bat-check, avoiding blinks in the middle of modes.
Any update on this project?
I’ve had a browser tab open for 5 months to remind me to come back to this… and now I don’t remember what, if anything, I needed to do.
I added tiny1634 support though, in part thanks to Mike C’s help. 
Well, sort off. I ran into big problem, I ran into myself… again. I After reading gchart’s thread on AVR 1 series I made a driver based on the ATtiny3217 for a specific project. After having built this driver and getting everything working I got back on working with the 1634 drivers, but they felt… old… Not motivating at all.
So the inevitable happened… All my 1634 drivers have been scrapped, new 3217 drivers have been designed in their place. I have new versions of Fat3 and Slim5 (now 5 amps instead of 4.5) and I’m currently moving over all firmware functionality to the 3217. Changed work conditions have slowed things down a little, but I’m working on it when I can. Giveaway is still active but will be these newer versions as I never finished the firmware for the 1634 based ones before inevitability struck.
Sorry for the wait, but hey, blame gchart! :innocent:
Slept on it a bit and have had a slight change of heart. I do have a bunch of these 1634 versions built, and as I won’t use them myself it would be a shame if they didn’t come to use. It’s better to close this giveaway, send off these drivers and do another giveaway once the new ones are done. When I get home tonight I’ll check how many drivers I’ve built and announce giveaway winners tomorrow. Firmware might not be fully completed with everything I want but the basic functionality working with multiple UI choices for all switch configurations.
Duplicate from post #2:
So, time to give away from drivers. Many interesting posts, don’t have drivers for all of them though. Hopefully not everyone has lost interest yet…
As mentioned, I’m working on 3217 based versions so the winners here can choose to get the current version or wait for the new version which is at least a month away. Possibly longer, things haven’t been going so fast lately… I didn’t finnish the 1634 entirely, but it’s working firmware with LVP and so on. No blinkies or special modes other than a true momentary mode regardless of switch type.
Main difference between current version is lower constant current rate before resorting to PWM. The current 1634 versions can go down to 150mA constant current, the 3217 versions go down to 16mA. There is also a special moonlight mode that doesn’t use PWM but it’s highly experimental (uses DAC output directly from MCU).
People I picked for drivers based on suggestions or other reason:
MascaratumB
Cereal_killer
CRX
MRsDNF
Sirius9
Let me know if you are still interested, and if you want the current 1634 version or wait for the 3217 version.
No worries. As you might have guessed from above posts, I’m moving away from the 1634. Do you need any 1634s? I can send a few your way, no cost to you. I have quite a lot of them, I don’t predict ever using them all.
Congratulations to all the winners 
Sorry for the late reply, I wasn’t receiving the alerts on e-mail!
And thank you for choosing me Really, thank you!
And congrats to the other winners
I don’t mind getting the 1634s and see how they work! I will give the feedback here when I receive it =)
Thanks and let me know what shall I do meanwhile!
Thanks for your input! Your input and videos about clicky switch functionality had a significant influence on my firmware.
Are you going to be using this driver in a clicky switch light, or one with an E-switch? I ask because changing UIs and settings is a little more tedious with clicky switch. It’s easy to accidentally turn off the light when doing multiple short off presses, and doing that will botch the sequence. It’s certainly doable, I do it, but how easy it is largely depends on the switch. Because of this it’s better I take the time to setup all clicky drivers to the user’s preferences from the start.
I’ll update post #2 with UI options later this evening. I have an embarrassingly large amount of UIs and settings to choose from so I’ll try to keep it short.
Thanks Mike! I am glad it helped Currently I wouldn’t be able to do those videos as I damaged the driver with the Crescendo UI :person_facepalming: Don’t ask, don’t tell!… So I’m glad I did them in time 
I will probably use it as clicky switch because it is easier for me to mod lights that use a pill and clicky switch! I assume the diameter is 17mm, right? If smaller I also have some candidates for it :partying_face:
Depending on the driver’s “architecture”, I could use it on the BlitzWolf BW-ET1 (e-switch), but that probably requires a good syntony between driver shape and host, which is difficult due to the host :zipper_mouth_face:
So clicky switch is probably the best choice so that I don’t damage it
BTW, it is “made” for reverse switches, right? Anyway, the light I will probably use it in is fit for reverse (a Convoy S2+ Desert Tan with metal button), not forward switch, so there will be no issues!!
I am not sure how, but I missed this thread from day one. I had to take a break from lights, modding lights and building drivers. But, now I am back and ready to roll.
I realize I am way to late to jump into this GAW, that is fine as I just hope that these drivers come to be. As much as I love the concept of the OMG FET+x 7135 drivers and as much as I love the latest firmwares from TK… there are many times that I fall back on fully regulated drivers for efficiency or because I do not want to cook a single led.
A 3 amp driver is great for a long running EDC, but the 4.5 or 5 amp driver is something that I really like the sounds of. I still use a bunch of 219b R9080 leds in my builds and mods for others and from time to time I still build P60 modules. In either case a full on FET is not a good idea, and I am not a fan of PWM as it finds the strangest times to be ever so slightly visible even though PWM frequencies have gone up to levels that are very hard to detect.
Moonlight? You are a man after my own heart! Maybe I am odd, but I think every light that may be carried must have a good moonlight mode. I like a moonlight mode that is so low that you can look at the die and not feel any eye strain, not leave any spots in your vision in total darkness and will not fully wake you at any time. New lights of any quality and value claim to have “moonlight” modes. Somewhere along the way that term has had subtle changes in translation. The new crop of truly wonderful lights like the FW3A, D4V2 and such have a low mode, not a moonlight mode! When I think moonligh, I think of lights like the ReyLight Pineapple, the triple 219b’s that I build with the H17f driver and Zebralight’s ultra low modes where the leds are on but are at such a low level that they really do only push light out 4 or 5 feet when your eyes are dark adjusted. Many of the new lights make me whence when I turn them on a 2:30am to get up.
Firmware… I really love a ramping driver! But, I think that there should be direct access to lowest and highest output modes from a single switch and I think that the light needs to have a memory mode as well. Again, if it is an EDC, I should be able to set it to the lowest or nearly lowest mode, place it on the nightstand and not have to think about how to get to the lowest mode at 2:30am. Thus the memory with a full range of output as it provides a single click to turn on the lowest mode as it would have been memorize at turnoff before bed. I do like set modes from time to time. The problem I find with set modes is that they are not always the best values for the build. So, one ends up building the driver, flashing the driver, building the light only to find that they need to take it apart again to reflash the driver because the mode spacing is not optimal for that build.
Odd modes… I think that every light should have 1 special mode… something like a bike flasher as in low/high levels with a duty cycle that favors the low level output. Why… I live in a tiny rural town with few street lights and it gets really dark. When I walk, I like to clip one on a pocket somewhere so I do not get run over! I really like the H17f for this, it has a level of output variability to it’s flasher mode. Meaning… the top does not have to be 100% and the bottom is variable with the top. It does not take full power. There is a process among drivers called target fixation. This is a bad thing, if you draw to much attention to yourself visually, a driver will work so hard in their mind to avoid you that they actually fixate on you and drive toward you. This more often than not results in motorcycle drives being hit. This is were the variable output is nice.
Mike, I hope that this makes sense… I also hope that there is some value in something I have said.
Matt
To be honest, I would have been a little disappointing if you didn’t use it in a clicky, I want you to try what you have influenced
Driver diameter is 17mm, drivers are dual sided (components on both sides) and can only fit a small Nanjg/Q-lite size springs. I use reverse clicky myself, but by looking it your videos at least some functionality works with either.
Makes sense! All modes in my firmware are fully adjustable/programmable. I have mode memory (actually a few different mode memory choices). The only thing I don’t have in the current 1634 driver firmware is blinkies. I’ll be making beacon and bike modes, I was going to make it for 1634 drivers but didn’t get around to it before switching MCU yet again, so that will be for the 3217 versions.
Been a through a bunch of MCUs now… 13a, 85, 84, 841, 1634 and now 3217. I think it will stop with 3217, at least for quite some time. It has more pins and memory than I can use… but I’m just sounding like a broken record now.
Look forward to being able to get my hands on these when they go production. I am almost 54 yo and my uncorrected eyesight is 20/800 and 20/850, corrected 20/30 to 20/35 depending upon the day. It really takes work for me to build drivers now, must have good magnification just to begin to think about building them. More options are always a good thing.
Ahah, clicky switch it is I am more comfortable with those anyway!!
That’s fine too, in the S2+ there is no problem when using double sided drivers, so I will use it in a new pill I will make just with this driver. Maybe on a Triple or with a single Luxeon V2
Or…maybe I can use it in the Convoy T2, in case the double sided fits well
Will you solder the spring on it? If possible, that would be better, so that I don’t mess with the heat in the components…I may be sloppy in spring soldering :zipper_mouth_face:
Thanks again
I’ve made the GND ring rather thick so they fit in all my convoy lights without needing to file down the retaining ring. I’ll put on a spring for anyone that wants it.