Anduril ... 2?

The problem with this solution is that we always end up getting into voltage check (triple click) when trying to access turbo which is real annoying especially under tactical situations where we need turbo access immediately.
This is the ideal and is what most UIs from premium brands like Thrunite, Olight, Acebeam, Nitecore etc. use. It’s the most intuitive and the majority of users like the ability for easy direct access to turbo.
As a compromise, I think this is acceptable. We still have direct access to turbo though it won’t be consistent with the industry standard double click to turbo.

Thanks for your hard work btw!

I prefer this method too. Most times I only need ceiling brightness, and when I do use Turbo it’s only for a few seconds then my light is too hot to hold.

This also allows the user to set the ceiling to Turbo level if they want “Off 2C” to go to Turbo.

I think I’m having a different problem. I’ve been using my Supfire M6 lately. It’s got four 30Qs and 3 XHP50.2s on a FET+1+15. It’ll run on full AMCs for a long time before it steps down slightly to a thermally stable level. So I initially set ceiling to max 7135s. The problem then becomes, I get a jump from about 6A to (guessing here) something north of 30 Amps (possibly much higher, but I can’t test). While the double-click to ceiling is nice and how I like things, I sometimes really want to ramp partially into the FET range but can’t. I have pretty nice control of everything from below 1 lumen to maybe 3000? And then a jump to 10K or something. So I can change the ceiling higher, but then my double-click from off goes much higher than I’d like.

I thought about it, and I don’t really think this is something Anduril should, or can in a practical way, fix. It’s also probably only really necessary on the crazy lights, beyond D4 power levels. If I get to the point where it bothers me enough on this light, I’ll just have to write in a change, and manually define 2C from off to always be a certain level, and let ceiling be whatever I want for ramping.

For the rest of my lights, I set ceiling to turbo.

Also, for “Ramp 2C : ceiling if mem < ceiling, or turbo if mem >= ceiling”, how could memory be higher than ceiling?

On lights like the M6 or D18, what I’d suggest is setting two different ceilings. Then you can pick one relatively quickly by choosing a ramp and then jumping to the ceiling. This is part of why I’ve kept the “change ramp style” function on a short button sequence. I mostly use it to select from two floors, but two ceilings works too.

Specifically, it might make sense to configure the stepped ramp so the highest regulated level is, perhaps, step 6 of 7. Or maybe even step 5 of 7. Or 6 of 8. Or whatever. The steps.py tool is helpful for doing stuff like this. I’d also configure the smooth ramp so it stops at the highest regulated level. Or maybe all the way up to turbo.

Greater than or equal to. So, if the user ramps up all the way and then double-clicks, it would go to full-power turbo. The greater-than part is mostly just a way to cover any obscure corner cases and prevent potential bugs.

Like, if the two ramps have different ceilings… the user could go up to the higher ceiling, then change ramp styles, and memory could theoretically be set higher than the ceiling. In practice, that’s not how it works since Anduril checks and changes the memorized level while changing ramp style… but it doesn’t hurt to handle the corner case even if it should never happen.

A lot of programming is about handling conditions which should theoretically never happen.

I’d argue that if you are looking for a light for “tactical” use, an Anduril light probably isn’t the optimal choice in the first place. There are already plenty of tactical lights with very simple UIs available for this use case.

I really like the idea of 2C always going to top of ramp, from both off or on. This is usually set to a much more usable level than a full FET turbo that can only be sustained for a few seconds. I’d use 2C from on much more often if it went to the top of the ramp since I rarely use full turbo on pocket rockets like the FWxx. If a user intends to use full turbo all the time, the top of the ramp can be easily set to turbo. 2H from off for turbo is a good compromise to keep it accessible if you need to go full blast for a few seconds for “tactical” reasons.

I finally received my EDC18 two days ago and have played with it since. And it met my expectations and even more, when configured the way I want it I believe it is the best UI on any of my flashlights.

As for Anduril 2 I see the need for the simple UI. I let my wife try it and she struggled with all the clicks, in particular separating 4 and 5 clicks. So when trying to activate “lockout” she often went into momentary instead, and she had to try several times to get out of lockout. I tried to teach her my way of doing it which is counting 2C’s like One-Two-One-Two for 4C and One-Two-One-Two-One for 5C, but that did not work for her.

The way I see it “Lockout” is a safety feature which most people probably would like to enable on a light, while Battcheck is more of a specialist requirement. I realise you would loose the new features of choosing where to start from lockout (4H floor and 5C ceiling) with 3C for lockout, but I believe it would be much easier for “normal” users to go in and out of lockout with 3C. I realise that one UI can’t be perfect for everyone, and each has personal preferences, but I would like to know why you concluded that 4C would be better than 3C for lockout after having tried it a bit? Could you elaborate a little on this?

And do you do wishes? :smiley:
I would really really really like to have the ability to enable the 2H to momentary turbo in Simple UI without raising the ceiling. Is there any way you can make this an enable/disable (with default disabled) feature? One of the really good things about Anduril is that it gives me direct access to 3 adjustable levels from off (floor, manual memory and ceiling), and to turbo when on. Normally I never use turbo for longer periods at a time, so the 2H from off seems like a really nice addition to get access to all four levels from off. I also believe that a lot of other “advanced users” would like to set up Simple UI in the way they like it by going through the advanced UI first, but then use simple UI as their default one. And I would hate to have to give up ceiling to achieve this.

Anyway, thank you very much for your dedication and hard work :smiley:

I’m not sure how many users have there lights on for long periods of time but how about a timer that can be enabled and disabled?

Lets say flashlight is turned on and no input is received for mins (programmable) then light shuts off.

I would prefer not to have the version check in simple mode. It is not an essential function and it could cause confusion if activated accidentally. Anyone who knows enough to want it can go into advanced mode to get to it.

Agreed. Even though I just read about simple mode, I simply forgot about it.

Or maybe activated by default for something like 10 mins but then to disable it or make any changes then that would have to be done through the advanced UI

Envinyatar

Titles
As king, Aragorn had many titles:

The Dúnadan
Chieftain of the Dúnedain
Heir of Isildur
Heir of Elendil
King of all the Dúnedain
King of the West
Lord of the Dúnedain
Envinyatar - “the Renewer”
King of Gondor
King of Arnor
High King of Gondor and Arnor
Lord of the House of Telcontar

For lockout,

click click click hold, confirmed by a flash sequence to confirm lockout is engaged, would be awesome.

We don’t want the firmware too confusing next to other brands, most use 4 clicks and it’ll be confusing if owning multiple lights

It has a sunset timer. Turn the light on, then click 5 times and hold the final press. The light then blinks once per second. Each blink adds 5 minutes to the timer. Let go when enough time has been added.

Then it slowly dims and eventually shuts itself off.

This setting doesn’t stick though. The timer is only active until the light shuts off.

I ment more for accidental activation. I known there is now a feature for if you hold the button it will not stay on high. But what if you don’t have it locked out and it clicks in you bag or pocket.

Muggles may forget to lock there lights out. Heck sometimes I forget too.

You could use the autolock feature that locks the light after some time of inactivity.

Since I use manual memory, am I correct in thinking I would no longer have any access to turbo except the momentary hold from off with this setup?

Personally I’m not at all interested in a shortcut to turbo from off unless it can be disabled some way (or is momentary). The ability to set the ceiling to a less pocket-scorching level is a big part of the reason I feel even slightly comfortable carrying a hotrod unlocked.

Autolock?

@Vbryanv

[/quote]

It looks like I still have so much more to learn. The only configuration I thought the only thing you could change durning for lockout was the ceiling/floor ofqq lockout brightness.

So when I adjust the minutes for auto lock config, I can use then light like normally and then during inactivity it will default back to lockout? Or am I more lost than I feel?

Has this been around long? 80% of my Andruil UI lights should have then UI from withing the last year.

Edit: After reading up a little seem like I have to reflash to the latest software to give it a try.

I may be fairly new but your software and the fact that you communicate with the enthusiasts is one of the reasons I keep buying flashights with your UI.

Keep it up

Yes, it will lock the light after the set amount of inactivity. Currently it is 10C/10H but that might change again, who knows. It’s not in an official release yet, you have to compile it yourself. None of your lights currently has it.