Yep, double-checked when I got that message too.
The files should be put in the top level of the specific project folder correct?
Someone mentioned on reddit about Halloween and making a flicker effect and I thought it would be neat to like triple click while in lightning mode and invert it so it dims every once in a while, don’t know if that would fill up too much space though.
Top level? I have all the files in one level, no sub levels, i.e. no sub folders.
When I first make the project it creates sub-folders within it, one of which contains main.o and a few other files that I’m actually not sure the purpose of. I put the Anduril files at the top level folder though.
Oh, I did that long ago. I delete main, merge all the Anduril files into one folder, and then add all the Anduril files. It's simple - no need to organize down to sub folders.
Here is a ZIP file of my current Anduril2 AS 7.0 build project: https://drive.google.com/file/d/1o74vZ7FaxO-jPsYxk1lFZR7KnbEwhzP3/view?usp=sharing
Download it into clean folder, unzip, load into AS7 and build.
Add this step between steps #2 and #3:
sudo apt update
And this step to access the files in windows explorer (mind the space and dot ” .” at the end);
explorer.exe .
(I have avrdude.exe and the USBasp-win-driver-x86-x64-v3.0.7 driver installed on windows)
Hybrid memory is an excellent idea, but shouldn’t it be available for both automatic and manual memory modes? I personally prefer the convenience of automatic-memory, and I don’t go to manual memory anymore because I feel stuck since it is not my personal default mode.
Here is my UI suggestion for “temporarily switching the memory mode” (hybrid mode):
[Removed by myself, I have revised my suggestion in a later post]
Also, could the timer be in increments of 5 to 15 minutes? My particular use case would be to manually set moon-mode at night for a couple of hours. 255 times clicks is a lot!
Also, this is my first post but I have been lurking Anduril threads since I found out about BLF and TK’s Emisar D4V2 review… and I bought one the same day, my first quality flashlight, D4v2 in sst20-4000k 
2 Thanks
It could be modified to do that, but there’s kind of a problem… heat. Lightning mode barely generates any heat, so it’s pretty safe to leave on. An inverted lightning mode, however, would overheat in under a minute on a lot of lights. So you’d have to make sure the top level is thermally sustainable, and then flicker downward from there.
That’s basically what hybrid mode is… it’s both.
I get the impression there has been a misunderstanding… possibly just me not understanding the idea. So perhaps I can clear things up by explaining the memory options a different way.
There are three different styles for brightness memory in Anduril 2. So after shutting off the light, there are three things it can do with the last-ramped brightness level:
- Always remember.
- Remember for N minutes.
- Never remember.
These are called “automatic”, “hybrid”, and “manual” memory modes.
But it sounds like you might be suggesting a fourth option?
- Only remember after light has been off for N minutes.
Is that correct? And if so, can you provide an example where it would make sense to do this?
Or perhaps the idea was to have a timer which starts when the user activates it in the config menu, and it temporarily changes the memory mode, and then after the timer expires, it goes back to the previous setting? So, like, it’s 9pm and you start a timer for 3 hours. You have 3 hours to use the light with a different memory setting. Then at midnight, it goes back to the original setting?
But that’s not how it works. The “N minutes” memory timer starts each time the light is turned off. So if you set the timer to an hour, but you turn it on every 45 minutes, it will always remember. It doesn’t forget until the light has been off for at least an hour with no button clicks.
Phrased a different way, a 1-hour memory timer means: If the light has been off for more than an hour, I probably don’t remember what brightness level it was at… so go back to the default level. However, if it has been off for less than an hour, keep using the same level it was at before.
It remembers brightness during each session, but resets to a default brightness afterward so it won’t do anything unexpected. No more accidental moon mode during the day, or accidental turbo during a late-night bathroom trip. If it has been on a shelf for a week, there’s no need to wonder what brightness it’ll turn on at… it’ll use a predictable default. Set the memory timer to match the attention span of the user, and it’ll mostly “just work” in an intuitive way without unpleasant surprises.
I’ve been trying to get the UI as close as possible to just “one click on / one click off” with no need to do anything else. That’s impossible, of course, without telepathy… but this seems to get it one step closer.
Yes, manual memory (the “never remember” mode) is when the timer is zero. If it helps, here’s a table from the documentation, explaining how to configure each of the three styles:
mem type manual mem manual mem timer
-------- ---------- ----------------
automatic off any
manual on zero
hybrid on non-zero
Thank you! The misunderstanding was on my part, my apologies… this is actually excellent! .
What I was suggesting the inverse of hybrid memory, temporary manual : whatever mode you are on, you can set a timer (10H—menu #3 o #4 ). Now your light is in temporary-manual and will always turn back on (from off) to same brightness level.
When the timer expires, the previous mode comes back.
But you might as well just go to manual memory … no real need for a new menu item.
[edited 2021-04 to make this shorter and to say… hybrid memory is the best!]
Just flashed my D4V2 with anduril 2. Very impressed with the improvements especially the momentary turbo with 2H.Very Good job toykeeper! Now i’d like to know if it’s safe to flash my KR1 (W2 green) with kr4-nofet firmware? Is my D4v2 adapter compatible? Thanks
Would be awesome if someone could provide a complete hex for flashing…
>hint, hint<
Wow…those are fresh!
Thanks!
Yes, it should work… and that’s the correct build for that light.
It’s not really done yet… those builds are only online to get some feedback from more people than the few who have already tried it.
Once it’s actually “done”, I’ll put some builds in the parent directory where all the anduril1 stuff is… and probably move anduril1 to a sub-directory.
Hello Toykeeper. Thanks for your great work in developing Anduril 2 (and Anduril before it).
I see several Anduril 2 hex files available since yesterday.
Are these a release version, tested and safe to use?
I do not see a complete diagram of the Anduril 2 interface and I fear that despite reading through most of this tread, without a guide like that I would keep forgetting / getting lost. Are you close to completing it?
Any progress on a Lume1 version?
Thanks
There is a text manual in the same directory, it’s takes a while to get through but that lays out the new actions and flow even better than a chart would IMO.
There isn’t a full UI diagram yet. It’s kind of a pain to make one with so many functions on it. Every time I try, it ends up turning into a table instead of a flowchart.
But there is at least a diagram for the simple mode…
Is it possible to revert to Andúril 1 after the upgrade to Andúril 2?
Sure, why not? As long as you got a hex file to burn...
That’s awesome. Just to reassured that as I remembered TK did mentioned it is kinda no U turn. Thanks Tom E.