I’ve seen it do that right after a flash, but re-flashing has always fixed it. I haven’t seen it work and then fail though. One thing I’d try if it keeps happening is to switch the fuse for clock speed and tell it to use the longer startup delay. IIRC there was an option for 4us vs 64us, or maybe it was ms… I forget. I haven’t tried though, because it has only failed like once every 20 times I flashed it… and not since several revisions ago.
Fixed, I think. It was using 16/64 for the blinks and 8/64 for the stutter… I just bumped the stutter up to 12/64.
I hadn’t really thought about it, but since 10/64 is “low”, I should probably keep everything except moon at or above that level.
I think it might be an important option. It could, for example, set the thermal step-down back to the original value (without the need to re-calibrate it after turning this option off). It could also quickly reset from “easy mode” back to a regular UI. Assuming the default is close to what you actually want, anyway, which might not be the case.
I suppose, but this is the first time anyone indicated an interest.
Perhaps, though I suspect some would find it annoying to have a second level of LVP which stops early. OTOH, it also sounds similar to one of the timer options I considered, except it’d be trigger by voltage instead of time.
That sounds nice, but I doubt there’s room. It would probably need to be configured at compile-time in order to fit. Might be possible, but I’m not counting on it. If it’s implemented, do you think it should really be first in config mode?
Also, for “simple mode”, does this sound about right?
- L/M/H (in that order) at 10/64, 30/64, 50/64. (~10 lm, ~180 lm, ~690 lm)
- No memory.
- No moon.
- No medium-press (so no hidden modes).
Medium-press is now a configurable option.
Currently, disabled-med-press acts like long-press, but maybe it’d be better to make it act like a short-press?
Unfortunately, not much. Less than 100 bytes.
I’m pretty sure that would bite people when it’s not supposed to.
I have no idea how it would tell the difference between a child pushing buttons a lot and the owner of the light trying to reset it to normal operation. It only has the power switch as input… and on that note:
Exactly. A lot of more advanced features really require an e-switch or a dual switch in order to be usable without sacrificing a goat. The power-switch-only interface is pretty limiting.
That first one sounds like the timer option which was already requested. I’ve been trying to better understand what people would use it for, so thanks for the extra detail. A smooth fade from moon won’t be possible though, since the control resolution is very coarse at the low end.
Stop-motion strobes would have to be fixed speeds for now. I normally have 12 Hz, 24 Hz, and 60 Hz on my EDC. Plus two self-ramping strobes which ping-pong across some fun ranges. But to make it truly adjustable I’d need an e-switch. The attiny clock is also not the most accurate, so it won’t be exactly the speed it’s intended to be. I think they’re still fun though, and they’re really small so I could fit several different speeds.
As usual, testing and feedback are welcome.