The Folomov 18650S has this sequence - dunno, some complained about it, some like it.
Does that light only have ‘next mode’ function? No ‘previous mode’ ? That would explain it for me.
Ahh, think so... Don't have one here with me to check, but pretty sure that's how it works.
MikeC, you’re not missing anything, I was - Press&Hold for up and Double Press&Hold for lower is much better. My early suggestion was more for a rudimentary cycling UI that doesn’t offer a method of reversing direction and I didn’t realize how sophisticated your’re driver was/is getting. Looking forward to it.
Things have progressed a little, I’ve managed to sneak in a bit of development time.
There are a few suggestions for battery check here, but not many on exactly how to do the battery check. I have methods from my old firmware and a few new ideas but I’m looking for suggestions. How do you want to do battery check? Looking for suggestions for both clicky switch and E-switch.
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!!