Optical programming seems the most promising. But a lot of work and time.
I want that in a later premium edition of the FW3A with 90 CRI Nichia LEDs not now
A sunrise mode, please no. I think it’s to hard to set with the lamp. And the µC cant sleep.
Hmm, I’ll keep that in mind in case the diagram ships with the light. For now though, the .svg file is in the repository, and should work in Inkscape (free, runs on several OSes).
Not sure I’m familiar with negative voting. Can you just run raw numbers of for an option next to it? Also if people cannot stop at B and C, what will it accomplish? And force stopping would not be desirable I don’t think.
Using my D4, I don’t feel it has to be perfectly on the blink. I like the reference point because the human eye is terrible at judging brightness-
I frequently can’t tell if my Skilhunt H03 (last mode memory) is on medium (70lm) or high (160lm) until I cycle through the modes. The difference in modes is 10hours vs 5 hours runtime.
As far as missing the channel blink, it could be programmed to stop there instead of just blink, then a new press would continue on in the ramp. But then, that would interrupt the ramp and all sorts of other issue. I don’t mind passing it going up then getting close coming back down, it means the lights output is just shy of maxed out on the 7135 chip so regulation is good. Stopping just over the blink of course has the FET engaged and you’ve entered into not-so-efficient territory. AS IF this were critical. In critical situations a spare cell should be readily available anyway, right?
So, I like the blink top and bottom, and the blink at the channel change. Where in the soup does that put my preference?
Out of curiosity, I tried making the smooth ramp blink every time it passed a stepped ramp level. This would make the number and placement of blinks configurable… but in practice it was mostly just annoying. Then again, the default config had 7 steps.