Anduril ... 2?

169 posts / 0 new
Last post
Klayking
Klayking's picture
Offline
Last seen: 1 week 4 days ago
Joined: 12/17/2018 - 09:54
Posts: 154
Location: England

Oh yes, some of my FW3As are way out with their voltage measurements. 4.4V on a freshly charged cell in one, and 4.1V when I put the cell in another. Voltage measurement tuning would be great.

trakcon
trakcon's picture
Online
Last seen: 6 min 10 sec ago
Joined: 01/23/2019 - 15:50
Posts: 311
bmengineer wrote:
I’m sure I’ll have more thoughts on this, but the first thing that comes to mind is to remove the blink at different stages in the ramp. They’re useful dev features, but they don’t add much to the usability, and people who don’t know what they are always think it’s a glitch.

While I understand your reasoning, I really like the blinks. For FET lights, it allows me to know when I’m leaving regulated and entering FET world. Sometimes I prefer to stay below that threshold.

Klayking wrote:
One thing I would really love to see in Andúril is the ability to explicitly set stepped levels.

This is a great idea.

Klayking wrote:
Voltage measurement tuning would be great.

Agreed.

Klayking
Klayking's picture
Offline
Last seen: 1 week 4 days ago
Joined: 12/17/2018 - 09:54
Posts: 154
Location: England

I would really hate to lose those ramp blinks on something like the D4. I always use them to avoid going over the FET threshold when I want to be efficient.

manithree
Offline
Last seen: 3 hours 26 min ago
Joined: 01/12/2013 - 01:08
Posts: 443
Location: Orem, UT, USA

My use case is probably small enough to ignore, but I’ll make the request anyway. I use an EC03 for cycling, especially in the winter. I would love a “bike” mode. This could be accomplished (at least) a couple of ways:

  1. Have the strobe modes (optionally) “remembered” by mode memory. If I click off in bike strobe mode, the next time I click on, I’m back in bike strobe mode. Even a click-click-hold is tricky with winter mittens on.
  2. A new, dedicated bike-light mode that defaults to bike strobe, but might also have a way to access ramping or stepped (non strobe) modes. Meh.

I’ve actually considered doing #1 myself, but I still haven’t gotten the source from banggood for the EC03.

Agro
Agro's picture
Online
Last seen: 2 min 25 sec ago
Joined: 05/14/2017 - 11:16
Posts: 6172
Location: Ślōnsk
Lux-Perpetua wrote:
freeme wrote:
Would like to see support for second e-swtich.

+1 Thumbs Up


+2.

I don’t think reducing output by default is a good idea. Being a muggle does not prevent one from wishing to have the best lights out there.
That’s why some buy 100klum lights from unreliable brands. And that’s why those who invested time in basic research buy 4000 lm lights from good brands.
When a muggle buys a 4000 lm flashlight but it actually outputs 1000 lm there’s a big risk of disappointment – and it’s likely that a muggle won’t be able to figure out that there’s a hidden switch that unlocks a ton of extra performance.
I think that the best way to make muggles safe is to:

  • offer overheating and undervoltage protection
  • include cell to make sure it’s a good one
  • include charging so there’s little incentive to remove the cell
  • lock the cell inside so it can’t be removed without a special tool (but make the tool available to tinkerers)
  • add features like the already mentioned output reduction when the light is close to some object. I know it’s hard to do perfectly but even if you can stop half of damage induced this way – it’s better to have it than not.

As to size – I don’t think that it’s a good idea to limit the size to 8K.
Now that there’s Attiny1616 port available there can be many more features in the lights that feature this latest chip.

M4D M4X
M4D M4X's picture
Online
Last seen: 6 min 12 sec ago
Joined: 03/19/2014 - 05:17
Posts: 8556
Location: Austria (GMT + 1)

sounds GREAT!

Idea:
the Muggle mode could have a lower (fixed) Templimit
and in "Pro" the limit can be raised

that way the full power is available shorter and safer - but still there

 all new deals are posted here: 

deals.m4dm4x.com

ask MARTIN@M4DM4X.COM - i will try to save you money!

bquinlan
Offline
Last seen: 2 hours 39 min ago
Joined: 04/19/2018 - 01:07
Posts: 118
Location: Madison, Wisconsin, USA

This all sounds great to me. Any interface becomes more cluttered over time. Smart designers know when to bite-the-bullet (byte-the-bullet?) and rethink them.

I do recommend coming up with a new name for the new interface. If you just add a 2 or Pro after Andruil it will be “abbreviated” out of existence in too many cases.

The LITE mode is an excellent approach, but I would like to see it kept really simple. Most people get into trouble by accidentally clicking an extra time or two and then they don’t know where they are or how to get back. In LITE mode nothing under four clicks should affect anything beyond on/off and brightness. I would be okay with a plain full-range ramp and nothing else, plus an 8H or 10H to get to the full-feature mode. If strobe or beacon needs to be available from LITE mode start those options at 4C or more.

I would put all of the configuration options outside of LITE mode. If a novice wants to customize they can toggle into the full mode, make the changes, and toggle back out, using the manual for guidance.

Put the change from ramping to steps into the configuration menus so that it’s harder to toggle by accident.

I would love to see a configurable timeout-to-lock option.

I like the current two-stage options when in lock mode, but I guess I wouldn’t object to always going through the lowest mode first.

Making the auxiliary controls consistent would be nice. Having the option to separately configure button lights would also be great, for lights that can support it.

Thank you for asking us for input on this! I look forward to using whatever you come up with.

Now I want someone on the hardware side to make an equivalent to Hank’s reflashing kit for the lights that have 8-pad connectors. Smile

Firelight2
Firelight2's picture
Offline
Last seen: 2 hours 30 min ago
Joined: 04/08/2011 - 15:17
Posts: 4069
Location: California

I would like to see an easier to access aux LED control for the brightest aux modes.

Currently, on a light like the Emisar D4, dim Aux LED mode is all you need to find the light in the dark, and it is efficient.

  • Bright aux mode is far too bright to be used as a “find the light” indicator. It’s bright enough to light up a room by itself and runs the battery down too fast to be left on all the time.
  • It is bright enough it would be useful for those who might actually want to light something up with colored light. Similar to how some lights from Nitecore have a red led that is easily controlled.
  • In order to be useful as an alternative light source like this, it would need to be a lot easier to turn on and off bright aux LED mode. Perhaps quad-click to swap from main LED to bright aux LED. And the configuration allowing this to happen perhaps could be enabled when configuring the light in settings mode.
  • Dim aux LED mode could be kept as-is.
Anthon
Offline
Last seen: 10 hours 31 min ago
Joined: 09/07/2015 - 10:33
Posts: 638

Please Toykeeper make Anduril easy to use and hide the configuration modes

less than 7 clicks shouldn’t change anything

changing aux mode from lockout should need 7 clicks like when unlocked (no more accidental aux mode change when you miss a click trying to exit unlock mode)

no more 3 clicks from on to change between stepped /smooth ramping

I like the idea turning on the flashlight after exiting lockout mode (4 clicks) without having to single click again

lawallac
lawallac's picture
Online
Last seen: 2 min ago
Joined: 01/04/2012 - 15:31
Posts: 459
Location: WI

I love vast interface, but have been hesitant to suggest a light because it may be overwhelming to non-enthusiasts or those that just want to KISS. I’d love to gift to family and friends some of the high output lights if they were able to be factory full power but still maintain a level of safety.

varbos
Offline
Last seen: 19 min 21 sec ago
Joined: 02/16/2017 - 07:36
Posts: 524
Location: Europe

How about an app – PC or phone – where you choose your UI preferences (ramp ceiling, mode memory etc) via toggles and sliders.

Then when you are ready to program the light, the app generates a morse-code style sequence of long and short presses; the preferences are encoded in this sequence.

You simply put your flashlight into programming mode (via a long press), then enter the sequence to program the light. The app can “play” the sequence visually (scrolling left-to-right) to help you with the timing. Like Guitar Hero!

Is this practical?

Klayking
Klayking's picture
Offline
Last seen: 1 week 4 days ago
Joined: 12/17/2018 - 09:54
Posts: 154
Location: England

There have been concepts of using screen flashes to program a flashlight. Due to an interesting property of LEDs, they can act like tiny little (inefficient) solar panels. Placing an LED flashlight bezel down on a phone screen that flashes out a sequence at max brightness should in theory be able to program the flashlight. I’d love to see this executed successfully, but I think there are limitations that have prevented it being successful so far.

YogibearAl
Offline
Last seen: 11 hours 1 min ago
Joined: 12/29/2019 - 03:38
Posts: 197
Location: WA

Maybe have an option for those flashlights with USB charging to be able to program from the USB port? I guess this is hardware dependent but would be so much easier than using pins etc…

Anduril has been an eye opener for me, makes a flashlight a bit more than a simple flashlight.

To me however like my cameras, I’d like to see custom memory modes. f1,f2,f3 f(function) for example. (preferably on a second dedicated function button)

I can customize for the purpose/role of the light

examples of possible custom memory modes,

f1 tactical – instant on/off at programmable brightness – on/off only (for a lot of muggles this is all they want. on/off)
f2 muggle2 – ramp/step with moon to x level brightness
f3 bicycle mode – instant on/off
fx instant sunset mode – programmable duration on/off
fy demo – rotate between ramp/flash, stepped on/off
fz star gazing mode – moonlight/warm on/off
f? aux only mode – on/off, rotate between color, or ramp rgb?

non – function mode = everything like today. Lets not lose any functionality.

Maybe have some preset modes for muggle like after a battery swap (for muggle). So if for whatever reason someone gets into a weird mode, they can always reset easily. I know my kids have clicked more than 7 times continuously, or put the light in momentary mode, and had to reset. They may not even remember to press the button for flash sequence to complete.

Then for pro mode – reset with button pressed through sequence like today – opens all settings/configurations

for the current Anduril, maybe make momentary mode, more than 5 clicks? Often times on a light I put in my pocket I tend to turn on lock mode (4-clicks), but accidentally put it in momentary mode and have to reset. Sad putting it next to each other in click sequence is easy to make mistake.

jon_slider
jon_slider's picture
Online
Last seen: 8 min 54 sec ago
Joined: 09/08/2015 - 12:20
Posts: 3240
Location: The Land of Enchantment

I propose naming the new version Anduril Pro

Possible Anduril Pro Configurations:

Anduril Pro Safe LITE
stepped, emulation of the Olight S Mini UI
ramped, emulation of the Nitecore D10 UI

Anduril Pro Safe BRITE
stepped: emulation of Novatac UI programmable modes
ramped: Nitecore D10 Ramping UI, plus blinkies

Anduril Pro Full BRITE
ramped: a trained operator can raise the temperature ceiling to 65C

Safe config has 35C temperature limit

Anduril Pro Full BRITE “Scholar” Mode config allows operator to raise the temperature limit to 65C.

Dekzter
Offline
Last seen: 1 day 12 hours ago
Joined: 01/30/2020 - 17:51
Posts: 19
SKV89 wrote:
Also I would still love to have a way to get directly to turbo from off. Double click to turbo or maybe double click to top of ramp and triple click to turbo.

Just wanted to make sure you’re aware that if you set the ramp ceiling to turbo to can then get to it directly from off. But yeah, it you want to also have a lower ceiling then that would require a change.

Klayking wrote:
I would really hate to lose those ramp blinks on something like the D4. I always use them to avoid going over the FET threshold when I want to be efficient.

Curious how you utilize this in real-world use. If you ramp until the blink and then stop are you good, or do you have to ramp back down a bit? Is there any way to take advantage of this feature in stepped mode?

Viperkeeper
Offline
Last seen: 2 weeks 2 days ago
Joined: 06/03/2017 - 15:36
Posts: 38

Could we get some programing options for power on state? It’d be nice to add a clicky tail switch or make something like a D4V2 into a twisty. Similar to having Biscotti or Guppydvr combined with Anduril and some added functionality of still having an e-side switch. Would love a tactical turbo start with the rear clicky and moonlight start with side + clicky.

Firelight2
Firelight2's picture
Offline
Last seen: 2 hours 30 min ago
Joined: 04/08/2011 - 15:17
Posts: 4069
Location: California
Klayking wrote:
There have been concepts of using screen flashes to program a flashlight. Due to an interesting property of LEDs, they can act like tiny little (inefficient) solar panels. Placing an LED flashlight bezel down on a phone screen that flashes out a sequence at max brightness should in theory be able to program the flashlight. I’d love to see this executed successfully, but I think there are limitations that have prevented it being successful so far.

I recall TK looked into this for Anduril and even put in some of the preliminary code needed to implement it.

The problem was that it was far too slow for firmware updates. It would have taken hours to download.

However, I could see an app being useful for changing custom settings since presumably much less data would need to be transmitted. But on the other hand, if you can change your custom settings just with a series of button presses on the light, why go through the effort to create a phone app to do the same thing?

Agro
Agro's picture
Online
Last seen: 2 min 25 sec ago
Joined: 05/14/2017 - 11:16
Posts: 6172
Location: Ślōnsk
Agro wrote:
Lux-Perpetua wrote:
freeme wrote:
Would like to see support for second e-swtich.

+1 Thumbs Up


+2.

I don’t think reducing output by default is a good idea. Being a muggle does not prevent one from wishing to have the best lights out there.
That’s why some buy 100klum lights from unreliable brands. And that’s why those who invested time in basic research buy 4000 lm lights from good brands.
When a muggle buys a 4000 lm flashlight but it actually outputs 1000 lm there’s a big risk of disappointment – and it’s likely that a muggle won’t be able to figure out that there’s a hidden switch that unlocks a ton of extra performance.
I think that the best way to make muggles safe is to:

  • offer overheating and undervoltage protection
  • include cell to make sure it’s a good one
  • include charging so there’s little incentive to remove the cell
  • lock the cell inside so it can’t be removed without a special tool (but make the tool available to tinkerers)
  • add features like the already mentioned output reduction when the light is close to some object. I know it’s hard to do perfectly but even if you can stop half of damage induced this way – it’s better to have it than not.

As to size – I don’t think that it’s a good idea to limit the size to 8K.
Now that there’s Attiny1616 port available there can be many more features in the lights that feature this latest chip.

Extended:

  • offer overheating and undervoltage protection
  • include cell to make sure it’s a good one
  • include charging so there’s little incentive to remove the cell
  • lock the cell inside so it can’t be removed without a special tool (but make the tool available to tinkerers)
  • (ADDED LATER) make physical design that makes accidental activation unlikely
  • add features like the already mentioned output reduction when the light is close to some object. I know it’s hard to do perfectly but even if you can stop half of damage induced this way – it’s better to have it than not.

wle
wle's picture
Offline
Last seen: 2 hours 45 min ago
Joined: 01/07/2015 - 13:49
Posts: 1892
Location: atlanta ga

one thing that annoys me about stepped mode is, if you get more than about 8 levels, it takes longer to go through them than in ramped mode.

maybe make it go from floor to ceiling in less than X seconds no matter how many steps there are

all i would really want is a muggle mode that works, even if it is less simple
( i have the muggle mode that randomly decides the temp is too high and reduces to lowest level after random seconds)

"You never have the wind with you - it's either against you, or you're having a good day."
    Daniel Behrman, "The Man Who Loved Bicycles".
It never gets easy, you just go faster.   
-Greg Lemond.
       ,ø¤º°`°º¤ø¸,ø¤º°`°º¤ø¸,ø¤º°`°º¤ø¸

Klayking
Klayking's picture
Offline
Last seen: 1 week 4 days ago
Joined: 12/17/2018 - 09:54
Posts: 154
Location: England
Dekzter wrote:
Klayking wrote:
I would really hate to lose those ramp blinks on something like the D4. I always use them to avoid going over the FET threshold when I want to be efficient.

Curious how you utilize this in real-world use. If you ramp until the blink and then stop are you good, or do you have to ramp back down a bit? Is there any way to take advantage of this feature in stepped mode?

So, my personal setup for the D4V2 is as follows:
Smooth ramp: Full range from level 1 to 150
Stepped ramp: 3 levels. Low is level 25 (~20Lm), high is level 105 (~1000Lm). This puts the middle level squarely on the max regulated level of 65 (~150Lm).

In addition, I set mode memory to always switch the light on at level 65. The fully regulated 150Lm is useful in a wide range of scenarios where I just need an arbitrary amount of light. It’s also convenient to get as much light as possible from the most efficient output range with a single click. The blink is useful if I’m ramping up and down and I want to know where the threshold is without turning the light off and on again. Before TK implemented the mode memory customization, I relied on the blink as the only way to get back to just under the FET threshold in normal ramping operation. I still do on my FW3As, which aren’t so easy to re-flash.

I usually have my D4V2 in the smooth ramp mode for general EDC tasks, but often switch into the stepped mode if I want a better idea of how much power I’m consuming when using the flashlight for longer periods of time. The low step is good for close up stuff at night, medium is efficient for walking, and high will slowly heat up and step down to a sustainable level, but it lasts a while unlike turbo (which is still accessible with a double click if needed). I seem to be fully utilizing both ramp modes and I really like my current setup now. The customization options of Andúril are fantastic.

Mocarny
Mocarny's picture
Offline
Last seen: 11 hours 30 min ago
Joined: 05/10/2019 - 04:03
Posts: 272
Location: Poland

I will give you my ideas tomorrow, but what about naming it Anduril Next?
This way it doesn’t insult our old Anduril version and its users, like in the Anduril Pro case

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3

Was going to reply to everything at once, but it would make a very long post… so I’ll split it into a few and try to keep similar topics somewhat grouped together.

First, the name:

0oklight wrote:
If you changed the name entirely …

… Hence I like Andruil 2 instead of name change.

I’ve been thinking the same. Different name means different UI, not just an iteration of the existing UI. So I think it should probably be “Anduril 2” to make it clear that it’s still mostly the same, but different enough to give it a version number bump.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3

These things are generally already done or at least in the plan:

Th558 wrote:
For anduril LITE make the key combination harder to exit.
Poguche wrote:
put emphasis on making it more difficult to change settings
Anthon wrote:

That’s in the plan. Thumbs Up

trakcon wrote:
I didn’t see stepped mode explicitly mentioned. Please keep that around. It’s my primary mode.

Yes, smooth/stepped is sticking around. It’s not yet decided whether it’ll be possible to have steps in the simple UI though. It could potentially use the current ramp style and number of steps, but change the floor and ceiling to a narrower range… maybe.

Agro wrote:
offer overheating and undervoltage protection

This is already implemented, and will be improved by replacing muggle mode with an overlay-style simple UI.

Lux-Perpetua wrote:
Submenu for manufacturer custom modes

This is already possible and has been done, but it happens at compile time.

YogibearAl wrote:
someone gets into a weird mode, they can always reset easily

The factory reset function does this. The user would still need to exit the simple UI after a reset though, to get access to the full feature set again.

freeme wrote:
support for second e-swtich.
Viperkeeper wrote:
Could we get some programing options for power on state? It’d be nice to add a clicky tail switch … tactical … with the rear clicky and moonlight start with side + clicky.

It already supports two e-switches, as long as they do the same thing.

It also supports an e-switch plus a clicky switch, where the clicky gives it momentary mode all the time. Side + clicky goes to moon. Enable START_AT_MEMORIZED_LEVEL to use it.

Beyond that, redesigning the UI to take advantage of multiple e-switches would basically make it a different UI… so it would be a different project. Not saying it can’t be done, but it’s out of scope for Anduril.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3
tristech wrote:
It would be cool if changes made in Advanced/Unlocked Mode (normal) could be persistent in Lite/Simple Mode. E.G. If you set aux to blue they stay blue.
Poguche wrote:
ability to change the ramp settings of the simple UI from the advanced UI
bquinlan wrote:
I would put all of the configuration options outside of LITE mode.

That’s definitely one of the options I’m considering. It would then be possible to configure the simple UI, but only while the advanced UI is active. For example, it could keep the aux LED settings and maybe the ramp type and manual memory setting, but set a different floor and ceiling in simple mode. It could potentially also allow setting the simple-mode floor and ceiling, though I’m not sure how the UI for that would work.



BurningPlayd0h wrote:
make 2H from lockout activate {manual} memory {level}

That’s an interesting idea which hasn’t come up before.

It could perhaps do “low-floor high-floor” when manual memory is off, or “low-floor manual-mem” when manual memory is on?

YogibearAl wrote:
putting it next to each other in click sequence is easy to make mistake

It may end up with gaps between some of the functions which require more than a couple button presses. However, most of the parts which people get mixed up won’t be enabled in the simple UI so I suspect this type of issue may become less common.

SKV89 wrote:
a way to get directly to turbo from off. Double click to turbo or maybe double click to top of ramp and triple click to turbo.

It’s something which has come up a few times. Normally I’d suggest setting the ceiling to turbo, since that’s kind of the point of having an adjustable ceiling. But perhaps there needs to be more discussion about the various tradeoffs here, whether it’s worth having a separate ceiling and a shortcut from off to turbo, and what would have to be sacrificed to make that happen.

Like, there’s the question of what 3C should be. It could be a turbo shortcut. Or it could still be battcheck. Or I’ve been thinking about whether 3C should go to lockout, to make lockout more convenient to access.

There’s also a question of what 2H should be. It’s currently “go to ceiling and ramp down”, but maybe it doesn’t have to be. It’s nice for symmetry and consistency, but I never really use it and I’m not sure if anyone else does either. Perhaps it could be mapped to something else instead. There’s no shortage of other functions which could benefit from a shorter button mapping.



bquinlan wrote:
Most people get into trouble by accidentally clicking an extra time or two and then they don’t know where they are or how to get back.

I’ve been thinking the battcheck function should exit after it finishes one readout, when the user is in simple mode, like the version check does. This may help people avoid getting stuck. Can’t do that with lockout mode though.

Klayking wrote:
candle mode is a bit too flickery

It depends on the light and the brightness level being used. The formula isn’t great at adjusting to the full variety of configurations where it runs. It could also really benefit from higher resolution in terms of time and brightness, to allow for smaller / smoother changes. If I figure out a good way to do it though, I’ll probably do it.

roostre wrote:
A voltage calibration function
Dr.Phillip wrote:
Voltage measurement adjustement.

This has come up a few times, and I think it’d be a good idea to add it. There might not be room on tiny85-based lights though, so it could potentially be tiny1634 only or otherwise be enabled on a per-device basis.

bmengineer wrote:
remove the blink at different stages in the ramp

The blink is only there on some lights, where it’s relevant. Mostly just on FET+1 designs. It’s not there on some other lights, and I’ve been wanting to remove it on more. However, it’ll still blink at the ceiling.

One thing worth mentioning though… With the blink gone, it’s much harder to hide imperfections in the joints between different ramp segments. If the slope changes, it’s much more noticeable. So it’s often not difficult to tell where the segments join, even without the blip… which is both a good and bad thing.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3
DarkShot wrote:
Is the intent to have it be fully functional on ATtiny85 equipped lights already out on the market?

I’m hoping that every feature it currently has will also work on tiny85 in Anduril2… but depending on how it works out, new features might require a bigger MCU.

DarkShot wrote:
compile-time options …

- The ability to have Simple UI off after initial boot/reset but still retain the functionality and option to enter that mode. Just an ease of use function for power users.

- *Option to toggle momentary on lockout be either lower of the two or how it functions currently, if such a thing is easily done and if folks like how it functions currently. No reason to toggle on device.

Yes, the simple/advanced default value will be configurable at compile time. And the current/other or low/high momentary lockout order should be a compile-time option too.

dave1010 wrote:
Would you consider moving development from bzr to git …?

At some point, probably yes. But not as part of this revision. That migration is a separate project.

Git is really not designed for the way I work, and the features tacked on later to address this are fairly shallow, so it’s going to be a very frustrating process. But Git won the DVCS wars, so it should happen anyway.

Would be nice if I could go back and have a long talk with Linus Torvalds back in 2004 or early 2005 before he made Git, to prevent him from making some of the mistakes he made. At this point though, it’s probably too late to fix those things because they’re too deeply ingrained into the Git ecosystem.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3

Rockenrooster wrote:
First thing that comes to mind is more sensitive thermal sensor. Realtime if possible. Would be useful for keeping hotrods safer from self destruction.

Like reducing current very quickly (within 1 sec, disable turbo, etc) until it’s under the set thermal limit.

Since the sensor is a hardware trait, I can’t change it in firmware. The most I can do is change the thermal regulation algorithm…

… which is very tricky to do well.

It was recently rewritten, again, with the help of pakutrai (08-15 User). The test results are posted here. It’s still not perfect, but hopefully over time it can keep improving.

In any case, the thermal code isn’t really part of the UI, so it’ll likely be unaffected by the UI changes.

lawallac wrote:
factory full power but still maintain a level of safety

Given that the D4 can start fires in like 3 seconds, this is a question of full power or safety. On some lights, it can’t really be both at the same time. However, on other lights like the LT1, full power is pretty safe. So it has different settings on different lights. When it can be safe at full power, it allows full power by default in the simple UI… but when full power is definitely not going to be safe, it doesn’t.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3
tristech wrote:
custom shortcuts (or even just one) … Offering the ability to customize the actual user interface (with custom shortcuts like this) would set 2.0 apart as a truly major upgrade, not just UI refinement
Poguche wrote:
a “reserved” spot in simple UI (like click-click-hold) where you can put one blinky mode of choice
YogibearAl wrote:
custom memory modes. f1,f2,f3 f(function) for example. (preferably on a second dedicated function button)

It’s an interesting idea, but depending on the details it may be getting into the territory of becoming a different UI. Like, it could let the user customize every button sequence, similar to the YLP Unicorn, but then it wouldn’t be Anduril… it would be something else. So it might be better as a separate project.

Perhaps there could be one blinky in simple mode, but I’m not sure if people would like that or hate it.

jon_slider wrote:
Pro Safe LITE / Pro Safe BRITE / Pro Full BRITE / Pro Full BRITE “Scholar” Mode

emulation of the Olight S Mini UI
emulation of the Nitecore D10 UI
emulation of Novatac UI programmable modes

It sounds like you should design a new interface which has these things. I’d suggest using a new name for it though, instead of Anduril.

Klayking wrote:
Lastly, I love the tint ramping on my LT1, but the shortcut isn’t as convenient as the brightness ramp. Not sure if this can realistically be improved much, but …

Yeah, I don’t know of a way to make it easier to access without sacrificing something more important.

manithree wrote:
a “bike” mode…
  1. Have the strobe modes (optionally) “remembered” by mode memory. If I click off in bike strobe mode, the next time I click on, I’m back in bike strobe mode. Even a click-click-hold is tricky with winter mittens on.
  2. A new, dedicated bike-light mode that defaults to bike strobe, but might also have a way to access ramping or stepped (non strobe) modes. Meh.

I don’t think a separate UI for biking is likely in Anduril, but a bike-specific UI could be created. For now, the closest it has is the strobe mode memory which can go directly to the bike flasher with a click-click-hold.

Th558 wrote:
a shortcut which always goes to strobe at max.

There are already two shortcuts to strobe from off:

  • Navigate to the strobe you want, in the strobe mode group. Then turn the light off. Afterward, a 3H action goes directly to that strobe, using the same settings you left it in.
  • For even faster access, after you turn the light off from strobe mode, click 5 times for momentary. Then simply holding the button activates strobe.

… and in the update, I’m also adding a thing to make that second option easier. Go to the strobe you want, then click 5 times to go directly to momentary. No need to turn the light off first.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 4 hours 22 min ago
Joined: 01/12/2013 - 14:40
Posts: 10445
Location: (469219) 2016 HO3
Lux-Perpetua wrote:
toggle between a safe, conservative and a high performance setting…
M4D M4X wrote:
Muggle mode could have a lower (fixed) Templimit

Not sure about having two temperature limits in regular modes, but perhaps it could do something like set the Simple UI temperature limit 5C or 10C lower than the Advanced UI limit?

However, given the issues with factory calibration (or lack thereof), that means a much higher chance that the Simple UI would think it was always overheating. So it could be a significant usability issue for the people the update is intended to help the most.

It’s something to at least keep in mind though, since a lower limit in simple mode would help with the goal of safety.

bquinlan wrote:
Put the change from ramping to steps into the configuration menus so that it’s harder to toggle by accident.
Anthon wrote:
no more 3 clicks from on to change between stepped /smooth ramping

I’d like to keep that one easily accessible, in part because I use it a lot. It’s supposed to be quick and easy to switch between ramp styles. Have heard from a few other people who switch back and forth a lot too, like what Klayking mentioned earlier.

Klayking wrote:
the ability to explicitly set stepped levels.

This is much more tricky.

Probably won’t happen in Anduril, because the UI for it would be a huge pain to use. A big part of why it works the way it does now (floor, ceiling, number of steps) is to avoid setting the levels explicitly. I’ve never seen a UI implement that well without requiring a separate configurator app, and a configurator isn’t feasible on most of the lights Anduril supports.

If you can think of a really slick way to configure the levels though, perhaps it would be feasible.

Lux-Perpetua wrote:
immediately step down when placing something in front of the flashlight

Agro wrote:

  • include cell to make sure it’s a good one
  • include charging so there’s little incentive to remove the cell
  • lock the cell inside so it can’t be removed without a special tool
  • make physical design that makes accidental activation unlikely
  • add features like the already mentioned output reduction when the light is close to some object.

varbos wrote:
How about an app – PC or phone – where you choose your UI preferences

YogibearAl wrote:
program from the USB port?

I can’t add these with a firmware update. They require hardware features which don’t exist on most (or all) of the lights Anduril supports.

RB2021
Offline
Last seen: 3 weeks 5 days ago
Joined: 07/07/2020 - 23:59
Posts: 6

I’m playing with my new IF25a which is my first Anduril light today.

While off: Changing the aux light brightness requires seven presses.
While in software lock out: Changing the AUX light requires three presses. I believe this should also be seven.

Here’s why:
I intend to use this feature to show a dim aux when in lockout and a bright aux when in normal mode. For me this is a safety function and lets me know at a glance which mode the light is in. I expect it will also encourage me to set the lockout at night when I put it on my night stand. However, I’ve already found I’m prone to accidentally changing the setting while trying to take it out of lockout mode. For consistency sake and to prevent user error, I feel both modes aux lights should require seven clicks to change. People might not prefer extra clicks but I doubt many people change their aux all that often. Maybe on a D4v2 with different style AUX lights? If I could somehow lock these settings I’d be happier but I’d be just as happy if it took 7 clicks in both modes. It’s too easy to accidentally change.

Thanks for all the work you do. Anduril is awesome and I love the name too. If we have to mix it up I vote for Eärendil to be the new name.

Scallywag
Scallywag's picture
Offline
Last seen: 9 hours 18 min ago
Joined: 01/11/2018 - 22:23
Posts: 1194
Location: Ohio, United States

ToyKeeper wrote:
However, given the issues with factory calibration (or lack thereof), that means a much higher chance that the Simple UI would think it was always overheating. So it could be a significant usability issue for the people the update is intended to help the most.

It’s something to at least keep in mind though, since a lower limit in simple mode would help with the goal of safety.


I think the thermal calibration is going to be one of the toughest issues making lights safe. As things currently are, basically every Anduril light needs to be configured first thing.

As for changes to Anduril, I’d like to set the light up how I want it and then turn off all the config menus. Temperature calibrated? I never want to end up in that menu again. Ramping set (instead of stepped)? Get rid of it. On my LT1, I actually frequently end up messing up either the tint ramping or switching into stepped ramping. I think the issue lies with setting the double-click from off to not be turbo. So I end up “triple clicking” instead of going “on” and then double-click (3C instead of 1C;2C). Double-checked it; my FW3A came by default with 2C from off to top of ramp, whereas the LT1 came with 2C from off to the maximum brightness it achieves. I guess I’ll go find the instructions to set top of ramp to max and try the FW3A again.

EDC Rotation: ZL SC62(w) | Jaxman E2L XP-G2 5A | Purple S2+ XPL-HI U6-3A | D4 w/ Luxeon V | RRT-01 | Purple FW3A, 4000K SST20
EagTac D25C Ti | DQG Slim AA Ti | Jaxman E3 | UF-T1 by CRX | Nitecore EX11.2
L6 XHP70.2 P2 4000K FET+7135 | Jaxman M8 | MF02 | Jaxman Z1 CULNM1.TG | Blue S2+ w/ ML Special
Unfinished: Supfire M6 3xXHP50.2, Sofirn C8F, Sofirn SP70
Others: Nitecore EC23 | Nebo Twyst | Streamlight ProTac 1AA | TerraLux LightStar 100

Pages