Anduril ... 2?

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.

Auto-lockout is already implemented:

  • Lockout 5C -> Auto-lock config (click N times for N minutes)
  • Lockout 5H -> Auto-lock off

Another benefit of using 3C for lockout instead of 4C is that it would be harder to go to auto-lock config by accident while unlocking the light:

  • Lockout 1H -> Momentary (lowest floor)
  • Lockout 2H -> Momentary (highest floor, or manual mem level)
  • Lockout 3C -> Ramp (mem)
  • Lockout 3H -> Ramp (floor)
  • Lockout 4C/4H: nothing
  • Lockout 5C -> Auto-lock config (click N times for N minutes)
  • Lockout 5H -> Auto-lock off
  • Lockout 6C/6H: nothing
  • Lockout 7C/7H: Aux LED config

+1 this right here.

I already changed the aux LED mappings from 3C/3H to 7C/7H. This makes them the same as Off Mode’s aux LED mappings.

Also considering making it 3C/3H to unlock and turn the light on, which is more convenient than “4C, pause, 1C/1H”.

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.

That sounds/looks pretty awesome to be honest.

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.

Bring back the “old days” with a solderable star that locks in the current settings?

What about something like a DIP switch to enable/ lock the config?

Pretty much my last real issue with Anduril right there. I’ve messed up my own settings, and sometimes switched to stepped ramping…

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.

This is from another thread

Allowing full power and the ability to change the Simple UI sounds wonderful

BTW, I forgot to say it earlier, but welcome to BLF!

Usually it’s a thing people mention in response to someone’s first post, sometimes with silly pictures, but I don’t always remember to do it.

Toy Keeper, is there any config being included to switch off thermal regulation?

It would stop issues arising on different models that behave strangely or they simply don’t need it.

For myself I sell some models mounted to a gun and would love to disable it, if using normally again have the ability to switch it on with the previously saved temp config

NarsilM had this and it was really useful for certain situations

I think everyone will have something which they don’t like or would like added, but it can’t do everything. If you want max power momentary you’d normally be aiming for a tactical model with dual switches. Anduril is usually used on a single side switch.

My customers have said that NarsilM Ramping is the best and simplest UI they’ve ever used.

As a seller I’m happy to just have the Simple UI that’s been mentioned.

Turbo in momentary could be difficult when turbo is only accessible via a shortcut if you don’t want to config max ramp. Could require messing around a lot with a code that had a lot already written.

I’ve mentioned thermal step down to be disabled since in the past it hasn’t worked properly causing many issues. As a flashlight seller it becomes super frustrating to bring in 30pcs of a model that has thermal issues and then have to try sell them.

I was told by Tom E that disabling it wouldn’t require much?

If it’s a big issue then I’m not going to worry but it’s nice when I’m buying to sell, not like others who only have to deal with a single bad purchase

I would talk it over with your legal team. A full FET flashlight without thermal throttling could injure someone or cause property damage. As retailer you will surely be the main target of any lawsuit, particularly if the manufacture has no legal presence in your country.

It would be in the Advanced UI and only knowing what you’re doing will deactivate it. It was an option in NarsilM

Not all models are high lumen though and heaps of models of all types are starting to use Anduril

There isn’t, but it wouldn’t be difficult to add something. It could, perhaps, use a value of “1” as “off”… and instead of saving a limit of 70 C or less, it would set the limit to 255 to effectively disable the thermal regulation code.

In the thermal_config_save() function, add a line just before the end…

if (therm_ceil < 32) { therm_ceil = 255; } else

That should make it so, if the customer clicks exactly 1 time in thermal config mode, it’ll set the limit to 255 C and prevent thermal regulation from ever activating.

Or you could set MAX_THERM_CEIL to 255 instead of the default of 70. That works too, and would be harder for users to put it into a dangerous configuration… since they’d have to click a couple hundred times.

OTOH, I don’t really want people blaming me when their light destroys itself… and I don’t think any of the manufacturers want headlines about their lights exploding. So it’s not an option I plan to include in default builds, but it would be relatively simple for a person or a vendor to add that.

Fair enough :slight_smile: I completely understand

Yeah, I never actually thought of just adjusting the thermal limit and setting a lower temp of the light.

If the premature step down has been fixed already then I don’t mind it. The previous builds on like the Fireflies E07 was a real fail imo, first step down was almost immediate even at top of ramp, activate a second time and it would behave as it should. This is what really put me off since I imported quite a few units.

There is a problem with that. A lot of times, momentary is used for short bursts, and if a combination of clicks turns momentary off, it defeats its purpose.
That’s why Surefires and Elzettas and other tactical flashlights have models with only momentary switches and no modes, because on emergency use, if you have to do 2 (or 3,4…) short turn ons then you would go out of momentary.

One solution would be to implement a kind of pseudo-momentary, like HDS. If you press the button from off, it turns on momentary. If you relase in half a second or less (for example), it registers a click, and it turns on as usual. If you extend the press, it keeps on shining on that same level until the button is relased.

That function should be enabled/disabled, as it prevents direct access to moonlight from off.

Edit: And it would not replace the true momentary, which is still very useful IMHO.