Great feedback, Josh V!
That defeats the purpose of both the 4 mode driver (being very simple with no configuration) and defeats the purpose of my proposed modifications (no longer needing multiple user interfaces in Convoy’s mechanical switch lights to suit novice and advanced users). The suggestions I propose would accomplish the goal of making the default configuration simple, and it would not have tactical strobe enabled by default.
To be clear, “clicks” on a mechanical switch light turn the light on and off. It’s not just sending signals to the driver like on an electronic switch. So, I’ll assume those are meant to be “taps” of the switch after the light has already been turned on.
I don’t think a double tap for moonlight would work well. The light would turn on in whatever mode, then after a double tap would change to moonlight. In my experience, moonlight must be directly accessible from off for it to be useful. Otherwise I just blind myself first before moonlight comes on.
A triple tap for battery check might be OK, but I personally would prefer a triple tap to be reserved for something I need more immediate access to, such as Turbo, Strobe, Bike Flasher (for crosswalks), etc. Battery check is something I only use when time is not off the essence, so I would prefer it take more taps (like the 10 I have suggested) so that double and triple tap shortcuts can be used for more time-sensitive functions.
That looks almost exactly like what I’ve proposed, just with 75C and 85C added as options. I don’t see much point in having them since most batteries cannot safely handle temperatures that high, but I wouldn’t be oppose to those options being present as they don’t detract at all from what I’ve proposed.
Not in this case. We’re discussing the drivers for Simon’s mechanical switch lights, and lights with mechanical switches cannot detect clicks and holds. They can only detect momentary interruptions of power, achieved by quick taps of the switch once the light has already been turned on.
I agree. Having tactical strobe (or any of the blinky modes) in the default configuration of the 12 group firmware is a problem. I think that simply making the 12 group firmware default to mode group 2 would be enough to eliminate the need for the 4 mode firmware entirely, but I would also like to see these additional changes I’m proposing implemented as well. I don’t think there needs to be separate “friendly” and “advanced” firmwares. The firmware should come by default in a friendly state, then the user can customize it if they choose.