it;s going to need a whole web page to explain it all!
it’s almost at the point now that you need [or it would be nice to have] a phone app to track all the config parameters
why not have it control them too??
wle
it;s going to need a whole web page to explain it all!
it’s almost at the point now that you need [or it would be nice to have] a phone app to track all the config parameters
why not have it control them too??
wle
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.
Support for dual e-switch would be great.
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.
I actually like the extra resolution on the voltage readout…
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.
I wish two switch for the ramp up&down or another separate button for cfg
What you’ve done so far looks almost exactly like what I want.
Thank you! I really look forward to using this.
—Bob Q
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:
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.
•3 click +1hold goes to strobe.
•4 clicks from off goes straight to turbo.
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?
It’s already implemented in the development version.
A few more updates in the dev branch…
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).
I don’t use turbo often so this helps a lot.
Thank You!
The rest is looking good also.
All the Best,
Jeff
Another change I’ve been considering… this one is simple, but potentially a bad idea. I want to know what people think:
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:
But there’s also a big drawback:
So I’m not sure if I should do it. Any thoughts?
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:
After:
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.