I vote for 10C/10H, since there are others out there that use that.
I there a reason for 10C vs 10H ?
I would think that 10H would work for going back and forth without the need to remember if I needed a H or C to change things.
Not sure about having lockouts or other functions with just 4C (well maybe strobe).
Does anyone actually need quick access to strobe? Or even use it at all?
Seems like that might be too easy to activate. 4H or maybe 6H seems less likely to the muggles to find by accident.
Clearly you are heading in the right direction vs the current version - Thinks I.
Makes my head spin trying to conceive a simple interface that’s just complex enough. Without accidentally jumping into never never land.
If you are running out of room, maybe sacrifice one of the other entertainment blinkies?
I can see the future now - A-ver 4.01a, only running on 64b OS - 512K flashlights….
That’s kind of the problem. I need to talk to some companies which asked for 10C as a shortcut to thermal config mode. If they don’t mind though, I’ll probably use 10C/10H for Simple UI stuff instead. Thermal config mode isn’t as important now that it can auto-calibrate during factory reset.
A big part of it is so we can tell people to use 10H to make sure they’re not in simple mode… and it won’t really matter whether they’re in it or not. Similarly, 10C to enter simple mode… and it again wouldn’t matter whether it’s already activated.
In the old version, 6C went back and forth between simple and complex. In the new version, 10H always goes toward more complex, while 10C always goes toward more simple. So there is no need to know where you are… only where you want to go.
This is to reduce confusion for both the user and for anyone trying to help the user. One-way actions are less ambiguous than two-way toggles.
Some people are pretty passionate about strobe modes, and think even “click, click, hold” is too slow. It’s part of the reason why momentary mode can now also do strobes. That way, it can activate as soon as the button is pressed.
Strobe modes aren’t enabled at all in the Simple UI. They’re completely blocked.
The general approach I’m using is… supported lights get as many of the new features as possible without removing old features.
Anyway, anything with attiny1634 still has plenty of room. It’s only a few tiny85-based lights which require compromises. And depending on how some other optimizations go, I might still be able to fit everything. I’ve noticed a couple more things I may be able to reduce in size…
It would be nice if the auto-lockout function worked in Simple UI. If I decide later on to raise the ceiling for Simple UI, the auto-lockout would help to avoid setting my pocket on fire.
There are dozens of supported lights. Only one is capable of receiving data from a phone. So for most of the supported hardware, a phone app isn’t even possible.
On the one light which could potentially do it, there wouldn’t be much point. The hardware is difficult to reflash and the manufacturer has not been good about using updated firmware, so the new features would only be available to a few people. It would also require removing a bunch of other stuff to make room.
I actually have some FSM code to handle two e-switches… however, it treats both as if they were one button. It’s meant for cases like having a side and tail switch on one light, not for having two e-switches side by side for different functions.
To handle the side-by-side case well, it would need to be a completely different UI. Some functions could be reused, of course, and that’s part of why I split the code into a bunch of different files… but the button mappings would have to be completely redesigned if there were two buttons, so it wouldn’t be Anduril. It would be something else.
Can you simplify the colors for the voltage readout ? There are too many colors currently. This level of granularity is overkill.
From full to empty it should go :
Green… Yellow… Red… Flashing red… off
This is all one needs, it is universally understood that green is full and red means empty. In between should be orange but since this does not exist, yellow will suffice.
Nobody knows what white, cyan, blue or purple mean in relation to battery level.
It’s already pretty simple… it’s a rainbow. The colors go in the same order as a rainbow, with low-power frequencies representing a low battery, and high-power frequencies representing a full battery.
One huge improvement I’d like to see if proper momentary activation outside of a dedicated single mode. One possible way to do this would be an option to change long press from of to be momentary instead of moonlight, or hold from off for ramp min and tap-hold for rampax.
For a general purpose EDC, but if you’re using Anduril on a thrower or a ‘work light’ that’s used in relatively bright environments it would be incredibly useful.
This is similar to Nitecore’s two switch UI - tap for on, hold for on until released. I think a lack of easily accessible momentary is one of the biggest pain points using single e-switch lights.
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).
