Anduril ... 2?

Mocarny · 2020-07-07T22:09:43.000Z

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 · 2020-07-08T01:42:11.000Z

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:

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 · 2020-07-08T01:43:43.000Z

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

Th558:

For anduril LITE make the key combination harder to exit.

Poguche:

put emphasis on making it more difficult to change settings

Anthon:

That’s in the plan. :+1:

trakcon:

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:

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:

Submenu for manufacturer custom modes

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

YogibearAl:

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:

support for second e-swtich.

Viperkeeper:

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 · 2020-07-08T01:51:29.000Z

tristech:

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:

ability to change the ramp settings of the simple UI from the advanced UI

bquinlan:

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:

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:

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:

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:

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:

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:

A voltage calibration function

Dr.Phillip:

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:

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 · 2020-07-08T01:47:03.000Z

DarkShot:

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:

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:

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 · 2020-07-08T01:48:42.000Z

Rockenrooster:

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:

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 · 2020-07-08T01:54:02.000Z

tristech:

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:

a “reserved” spot in simple UI (like click-click-hold) where you can put one blinky mode of choice

YogibearAl:

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:

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:

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:

a “bike” mode…

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.

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:

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 · 2020-07-08T01:58:15.000Z

Lux-Perpetua:

toggle between a safe, conservative and a high performance setting…

M4D M4X:

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:

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

Anthon:

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:

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:

immediately step down when placing something in front of the flashlight

Agro:

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:

How about an app - PC or phone - where you choose your UI preferences

YogibearAl:

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 · 2020-07-08T04:38:07.000Z

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 · 2020-07-08T04:50:04.000Z

ToyKeeper:

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.

Dekzter · 2020-07-08T04:56:14.000Z

ToyKeeper:

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.

This is a great idea TK! The 2H shortcut is so easily accessible but it currently does something mostly useless (IMO). Perhaps this could be used to go straight to Turbo from Off?

Klayking:

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).

The customization options of Andúril are fantastic.

Pretty slick setup Klayking! I’m constantly tweaking mine as well. I like what you’ve got going on here and I’ll probably adopt something similar. I’ll likely use stepped mode to have a dedicated max regulated level as that will let me take advantage of the efficiency without having the blink in smooth ramp. I’d like more than 3 steps though so I’ll have to do some math

Agro · 2020-07-08T05:01:06.000Z

ToyKeeper:

Lux-Perpetua:

toggle between a safe, conservative and a high performance setting…

M4D M4X:

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:

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

Anthon:

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:

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:

immediately step down when placing something in front of the flashlight

Agro:

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:

How about an app - PC or phone - where you choose your UI preferences

YogibearAl:

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.

Yes. But your feedback matters to manufacturers.
If you feel something listed above makes sense you can communicate that to them - and it’s likely that some future hosts will get such support.

Klayking · 2020-07-08T09:38:17.000Z

ToyKeeper:

Klayking:

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.

I agree, coming up with a slick system for this on a single button UI is tricky. Here’s the simplest I can think of:

Enter step config mode with whatever shortcut is used and the light will flash once then start buzzing as it currently does.
In config mode, press nothing: the buzzing will stop and config will exit.
In config mode, press once to set the lowest step at output level 1, and keep clicking to raise the level of this lowest step.
When happy with the lowest step’s output level, wait a moment and the light will flash twice to indicate step 2 config is starting, followed by more buzzing.
Step 2’s config will start at the same level you clicked to when setting the first level. Clicking nothing will cause the config to exit and save your single step. Clicking once will advance to one level beyond the first step, and more clicks will keep moving up in brightness.
Repeat the process of adding more steps, each brighter than the last until you no longer want any more steps. Allow config to exit.

Thanks to continuing on from the last step, I don’t think this will be anywhere near as painful to config as my initial idea of bashing out a number of steps, then a number between 1 and 150 for each step. I can’t see this taking appreciably longer than the current step setup to configure, though there is indeed a slight increase in complexity. As this would be located within the advanced mode though, I think the extra control over your stepped levels would be worth it. I’m interested to hear what everyone else thinks about this though.

Poguche · 2020-07-08T09:37:17.000Z

ToyKeeper:

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.

I think this is neat, and have an idea.

First, to have less levels only for this menu (let’s say 30, with a known level for each mode that doesn’t use PWM, so you have a reference. Maybe with a formula you can relate the levels from the 30 ramp and the 150 ramp, like multiplying by 5, except level 1 that remains the lowest). This reduces the ammount of clicks and still allows room for enough choice.

You enter configuration and on the first ‘buzz’ you enter the number of modes (also allowing a single mode, that would be nice). Now it asks as many ‘buzzs’ as modes you have put, and you just click from 1 to 30.

If you configurate more modes than you had previously, it remembers the modes you had on first place (if you don’t touch anything during the buzz), and adds more on top. If you eliminate modes, it eliminates starting from up, and deleting the highest ones. You can also edit just one mode, leaving the rest as it was just like you can do now.

For a typical 4 mode configuration, let’s say that you need about 4 + 2 + 7 + 12 + 25 = 50 clicks as an example. With the current interface, seleting 4 modes, floor on level 10 and ceilling on level 125 you need 4 + 10 + 26 = 40 clicks. Not that much of a difference and you get to choose with more flexibility, although you give up your 150 levels (just for stepped, not for ramp). You can’t stop that precisely on the ramp anyways.

In addition, you can even configure special modes, such as candle mode, to numbers higher than 30, or with holds instead of clicks. The brightness of said candle mode (or freq of strobe or beacon…) would be adjusted from the original special mode location.

Maybe this last thing is overcomplicating it .

treellama · 2020-07-08T11:10:34.000Z

I’d like to see LVP for indicator lights. I think it was on your list before, pending a rewrite, and this is a rewrite

JaronRH · 2020-07-08T14:09:53.000Z

If we’re talking about breaking changes, I’d like to really push the envelope and suggest something really different! As more and more flashlights are including built-in charging via USB, I think it would be great to use the USB interface for configuration as well. The most versatile method would be to have the USB interface mountable as a flash drive. That drive could contain 1 (or more) configuration files (JSON?) that define the configuration, available modes, etc. This way, anyone could use their computer to modify the configuration (directly or using a GUI). Could even allow developers to flash updates over the USB interface too!

This would solve the problem of accidentally getting into configuration mode, allow for broader updates, and allow for easier control of the configuration. Not to mention, you could share configuration templates.

RB2021 · 2020-07-08T14:16:06.000Z

JaronRH:

If we’re talking about breaking changes, I’d like to really push the envelope and suggest something really different! As more and more flashlights are including built-in charging via USB, I think it would be great to use the USB interface for configuration as well. The most versatile method would be to have the USB interface mountable as a flash drive. That drive could contain 1 (or more) configuration files (JSON?) that define the configuration, available modes, etc. This way, anyone could use their computer to modify the configuration (directly or using a GUI). Could even allow developers to flash updates over the USB interface too!

This would solve the problem of accidentally getting into configuration mode, allow for broader updates, and allow for easier control of the configuration. Not to mention, you could share configuration templates.

While that sounds amazing, I think it would require some significant hardware changes. If there’s no flash storage/USB controller built in and I doubt any lights on the market have this, then there’s nothing to program this feature set for. I’m not an expert on flashlights though just my take as a computer nerd.

JaronRH · 2020-07-08T14:36:44.000Z

While that sounds amazing, I think it would require some significant hardware changes. If there’s no flash storage/USB controller built in and I doubt any lights on the market have this, then there’s nothing to program this feature set for. I’m not an expert on flashlights though just my take as a computer nerd.

You are right. There would need to be a USB host added to handle the communications (such as the MAX3421E). There is storage available though it is probably just EEPROM and not flash. (I personally have no experience with flashlight firmware - although I’ve looked at the Arduino code. I primarily work with ESP8266 and ESP32 chips which have WiFi. I can store files on the flash as well as host a full website for configuration.)

Additional ideas:

Add support for OLED display’s to show things like level, battery, etc.

mr_magoo · 2020-08-05T11:57:04.000Z

First of all, thank you for all of your hard work bringing us these awesome U/Is!

I love anduril and have gotten really used to it but would still love to see you offer a second version. We would get used to it pretty quickly im sure.

I havent yet read through all the comments so I dont know if this has been mentioned.

Could we pretty please have a simple version of anduril that:

1) Is always automatically locked out after turning off? Unlock would be a double click, which also turns it on to a level you can choose. Always just a double click to turn on the light. This will solve all accidental turn ons and eliminate so many button presses for theose who use lockout regularly. (Another way of putting is is one click is batt check, 2 clicks turns on light to memorized mode)

2) Still has quick, easy access to full brightness?

This would be achieved by using the following:

From off:
•One click would give a moonlight level bat check and would be a notice that light is locked out.

Holding the button down (1h) from off/when locked out, is momentary, as usual.

Double click turns on to your last used mode.

1 click + 1hold (is that called 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.

From on:

•One click turns off.

•Double click toggles between turbo and memorized mode.

•3 clicks to toggle stepped /smooth ramping just like old anduril.

•2 clicks +1 hold= tint ramping just like old anduril.

All other functions gone, or in a more advanced u/i that is hard to access.

I dont like lights that have a hard to access buttons like in zebralights. Though they are nice for keeping the light from turning on accidentally, they are hard for my fat fingers to operate easily when there are multiple button presses needed, especially when cold and/ or when wearing gloves (which is the case alot here in the icebox of Colorado) so that’s why I like the fw series so much. But the accidental turn ons are an hourly thing with me if I dont lock out. Its a little tedious having to click 5 times each time i want to use the light (quad click to lock or unlock,+ one click to either turn on or off, plus another to adjust brightness if neccessary. Thats alot of clicking every time I want to use my light (which is alot, every day).

Whezzel · 2020-07-08T19:15:29.000Z

manithree:

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

Check out this post: https://budgetlightforum.com/t/-/62655

It has info related to the firmware that runs on different lights, and how to find the source code.