As someone who uses lockout a lot, any improvements to this mode would be great:
> Harder to change the Aux lights (up from 3C to 5C maybe?)
> Maybe a shortcut to get out of lockout? For instance if you’ve been on 2H mode and then double click to unlock. I find the 4C to unlock can be a bit fiddly in the heat of the moment when you want to go from momentary to unlocked.
Otherwise all looks great can’t wait everything else I would have suggested has been mentioned. Voltage calibration, better muggle for family and friends, harder to accidentally activate the wrong thing, etc.
How about this?
Light is always automatically locked out when turned off. Another way of saying it is single click does nothing (except a single cycle batt check)
Double click turns it on to memorized mode.
2H turns on to moonlight.
3 short clicks, instead of being batt check from off, goes to top of ramp.
Thread was TL;DR so I’m unsure if someone brought this up. Would it be possible to add a function to calibrate voltage, similar to how we can set temperature?
Moved Simple UI button mappings from 8C/8H to 10C/10H.
Removed the tenclick thermal config shortcut, since it’s not really relevant any more.
Changed sunset timer’s time unit from 10 minutes to 5 minutes.
Made lockout’s momentary moon always use the lowest floor first, and highest floor second.
Made lockout’s momentary moon use the manual memory level on second click, if enabled.
Added support (finally) for 1-step ramps in stepped ramping mode. It uses a level halfway between the floor and ceiling, so there is no need to click a ton of times to set floor or ceiling to a middle level. This also means Simple UI can be reduced to just 1 brightness level if desired.
Fixed bug: In lockout mode, main LEDs would stay on while setting aux LED mode.
Reduced ROM size a little by refactoring some code.
Enabled voltage correction on 2 of the 3 build targets where it had to be disabled before.
Updated the text manual.
Most of what’s left involves writing documentation and making new UI diagrams. I’ll probably write up a tutorial with a bunch of diagrams to show different levels of complexity, so people only need to go as far as they’re comfortable.
The full UI diagram may be a little tricky, since more shortcuts were added and there’s even more info to include. I might change the layout quite a bit to make things fit.
There’s also still a question of what to do with 2H from off. It’s currently “go to ceiling level and ramp down”, but that doesn’t seem to be a function anyone uses. So there’s an open slot, and I’m not sure what it should be.
What I always didn’t like: from off, 2C brings you to max ramp. No direct shortcut to turbo. From on, 2C goes into turbo. No shortcut to max ramp. In my builds I have changed this so that 2C always goes to max ramp (without memory) and 3C to turbo (moved every other mapping one up).
Another change I’ve been considering… this one is simple, but potentially a bad idea. I want to know what people think:
Swap battcheck and lockout, so 3C = lockout and 4C = battcheck.
I wanted to do it this way originally, but instead I used the same mapping as NarsilM to be more consistent across projects. But now I’m thinking about going back to what I wanted before.
The benefits would be:
Lockout is faster to enter / exit… which matters, since lockout gets used a lot.
Batt check and other blinky-group modes aren’t used as much, so they don’t really need such a fast shortcut.
But there’s also a big drawback:
Would be a pain for anyone who has spent a lot of time with Anduril 1 or NarsilM.
I could go either way. I probably use lockout more often so having it be 3C would be advantageous but as you say… I’m so used to 3C being batt check.
Side note, and sorry if this has been talked about before, but what about a user-enabled option for auto lockout after a set time period? Edit: catching up on the thread now and reading up on previous conversations.
Also considering some other remappings… but also not sure, because it breaks compatibility again and that might be annoying.
Before:
Ramp 4C -> Config
Ramp 5C -> Manual memory on
Ramp 5H -> Manual memory off
After:
Ramp 4C -> Manual memory on
Ramp 4H -> Manual memory off
Ramp 5C -> Momentary
Ramp 5H -> Sunset timer +5m
This would make manual memory easier to access, and improve consistency because 5C would then go to momentary mode from Off, Ramp, and Strobe… and the sunset timer’s time unit (5m) matches the number of clicks (5H).
However, it again has the potential to cause confusion for people who used older versions, or who use both old and new lights. I don’t want it to be annoying to switch back and forth between old models and new models.
If light auto locked immediately, and 2c was unlock which turns on to memorized ramp, 1 click could be batt check. In other words 1 click wont turn on the light but will give 1 cycle of blinks indicating batt volt status. 1H could still be momentary bottom of stepped ramp.
Double click to unlock is super nice. Not too cumbersome, but still has reliable lockout.
RE: backwards compatibility, this is an issue but maybe not as bad as people think, we can flash the new version (if compatible) or adapt - and those that would really struggle with it would arguably be in muggle mode or buying different lights anyway?
[quote=lazerEagle]
RE: backwards compatibility, this is an issue but maybe not as bad as people think, we can flash the new version (if compatible) or adapt - and those that would really struggle with it would arguably be in muggle mode or buying different lights anyway?
[/quote]
I think the biggest problem I would have would be when I'm switching between my old Anduril lights and my new "Anduril 2" lights.
I still think Glamdring would be a good name for it.
The new Simple UI does that. In that mode, all configuration is locked. Nothing can be changed without switching to the advanced UI with a 10H action (click 10 times, but hold the final press).
Even in the advanced mode though, the config menus are harder to reach by accident. It requires more clicks, and there are no other actions nearby so it doesn’t happen if the user’s count isn’t quite right.