Anduril ... 2?

[gregor]

Thank you for your answer.

Yes, aux leds are changing color, when flashlight is off.

I wil try 7 clicks method.

Kind regards

[joechina]

Little problems with Andúril
1lumen (Netherlands) und Darren Yeo - Tech, Tools % Tutorials (Australia)

1Lumen Flashlight Hangout #1 (With Darren from OZ)

[ToyKeeper]

@joechina

Little problems with Andúril
video: 1lumen Flashlight Hangout

The video is 2 hours long, very quiet, and has no subtitles. What specific points did you want to share from it?

[joechina]

When you click on the link they should talk about things non flashlike people don’t care about.

(the video should start at a time mark)
Edit: I see the time stamp is f…ed
from ca. 53min onward

[SammysHP]

They are just complaining that Anduril is too hard to use in real life. When they needed light, they were lost with the UI and ended up with a non-working flashlight.

[ChibiM]

@SammysHP

are just complaining that Anduril is too hard to use in real life. When they needed light, they were lost with the UI and ended up with a non-

Lol. I just came here to ask a question, and see our video posted here… Just shared my personal opinion, and experience…

Just a quick question to @ToyKeeper .
I had a custom firmware built by gChart on my Emisar D1 v2 with FC40 for testing purposes. Today, I wanted to put the original Anduril 2 version back on, so I checked your list Index of /torches/fsm/anduril2 and another website, and none of them had a working firmware.

So I asked on Reddit, and somebody said I need the DM11 12V, which fortunately worked.
My question: could you please add that firmware to the D1 v2 list as well?

[bobvoeh]

I have a D1 v2 with FC40 and its running anduril.2022-10-21.noctigon-dm11-12v.hex
It’s what it came with.

[Quadrupel]

How about to add timed turbo stepdown?

[ChibiM]

Yeah, that one works… the 3 actual D1 v2 firmwares don’t. So it might be helpful to have that DM11 12V version in the D1 list as well, with the correct name. D1 v2 12V for example.

[thefreeman]

Several models use the same firmware, there would be a lot of duplicates if there were a firmware for each models.

[ChibiM]

@thefreeman

t of duplicates if there were a firmware fo

Well, then they could be added to all of them

[ToyKeeper]

@ChibiM

Emisar D1 v2 with FC40 … somebody said I need the DM11 12V, which fortunately worked.
could you please add that firmware to the D1 v2 list as well?

First I’ve heard of it.

I used to try to keep track of this sort of thing manually, in the PRODUCTS file. That quickly got out of hand though, since there are a lot of cases where the product name and the build target name don’t match, because manufacturers do all sorts of crazy things and don’t tell anyone. Sometimes a single product can run several different firmwares and the choice depends on factors the user may not even know… like which particular driver type or hardware revision the light was built with.

So I added a numeric ID for each individual build target, and added that number to the Version Check function. That way, people can ask the light what flavor it is, and be assured they’re getting the right answer. Just look up the number in an auto-generated MODELS table, to get the name of the build target it uses and the type of control chip it needs to flash.

And to guide people through that process, I made a short README file which should show up at the top if the page when looking at the .hex files. Here’s what it says:

@README

How to figure out which .hex file to use

1. Use the version check function to find out which flavor of the firmware the light shipped with. It should blink out a date and maybe a 4-digit number after the date – YYYYMMDDNNNN. Write this down. Version check is 15 or more clicks from off.

2. Match up the 4-digit NNNN number in the MODELS file.

3. Find the newest firmware for that model. You may need to scroll down to reach the newest files.

If the version doesn’t include a model number, it’s older, but you could
still look up the model in the PRODUCTS file to see which version it
probably uses:

~toykeeper/flashlight-firmware/anduril2 : contents of PRODUCTS at revision 659

TL;DR: I can’t fix it in the manner requested, because it’s out of my control. But if you read the readme, there’s a different solution which is simple and reliable.

[joechina]

But for new models you should also search other developers in case the model number is missing. Or ask here in BLF who has a firmware.

e.g. I couldn’t find 0714 on TKs Modellist, tought I was to dum to count.

Firmware Wurkkos TS10
I found 0714 on: gabe on launchpad it is from @gchart

https://bazaar.launchpad.net/~gabe/flashlight-firmware/anduril2/view/head:/ToyKeeper/spaghetti-monster/anduril/MODELS

[ToyKeeper]

@joechina

for new models you should also search other developers in case the model number is missing.

Short-term, yes. I got pretty behind on things due to some personal issues, so there are a few build targets I don’t have yet. But I’m working on getting people’s branches merged soon.

[ChibiM]

Thank you @toykeeper. I understand, and that makes sense.
So, if people are looking for one that is not on the list, it’s probably best to just ask…

[ToyKeeper]

@ChibiM

if people are looking for one that is not on the list, it’s probably best to just ask

Yes, if the number shown in Version Check isn’t on the list, it’s probably best to ask. It’s probably a new model which hasn’t been merged yet.

But most (like your D1) are on the list… even if not under the name you might expect.

---

Edit: I just noticed this post is comment #1337. Leet.

[wolfgirl42]

@ToyKeeper I thought I should put some of my general thoughts on testing different builds here instead of getting in the way in threads where it’s not relevant…

I like the new change in 710 to the post-off voltage reading, but it still has a couple of issues:

• If the off aux mode is on high, it seems weird to let it drop to low even if the light was only used on moon mode
• In general and related to the above, there should be a logical separation between the aux voltage mode such as a gap of maybe half a second or so(?) where the aux are entirely off before entering the normal aux mode, to make it clear something specific is happening. I tried to write a way but it ended up becoming too complicated to be worth it for me.
• blink_once() still causes voltage aux to activate afterwards (e.g. locking/unlocking the light), as does anything else that uses set_level() in any way not related to user-operation of the main emitters, primarily for a short time. In general including some of my own hacking on it, I came across a few edge cases already enough that I think the easiest way might be to have a variable that can be set by operations that call blink_once() or similar methods that use set_level() but shouldn’t trigger voltage aux, so it can be something like skip_post_off_voltage=1; set_level(foo);, then when the voltage aux would have activated, instead, it is skipped and skip_post_off_voltage reset.

[SammysHP]

Wouldn’t it be enough to limit the readout to the X to off transition where X is a set of states to be determined? This would skip some special cases and momentary modes, though.

[wolfgirl42]

Yeah, that might actually be simpler. {ramp, strobe} mode => {off, lock} mode to activate it. I ruled that out as an approach earlier because I came up blank on a way to accurately determine the previous state when in off/lock state, but if that was doable then it could go in EV_enter_state which would bypass a lot of the current weirdness, and if that could be done that might be the most efficient way, and would bypass the need for prev_level altogether.

[joechina]

Just for the people who don’t read on
21700 D4KTi COLORFUL version is available - #5924 by ToyKeeper and following.

Anduril2 is now (2023-05-10) on #657 and there is an additional version Anduril-Multichannel from #700+ on.

TK updated the manual to fit both versions in Rev. 706
(Edit: Since it’s 706 the new manual is at the moment in the Multi-Cannel branch only)

Wurkkos gets the model IDs 0700 to 0799 (TS10, TS11, fc13, emisars added)
MODDELS.txt was updated

Andúril 2 from TK
Rev. 657 (2023-03-28)
https://code.launchpad.net/~toykeeper/flashlight-firmware/anduril2
Anduril2 changes History
https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/anduril2/changes/
Some late changes:
→ new Tactical mode
→ strobe modes got 4C to go backwards
→ low bat warning on single color aux LEDs

New Andúril multichannel from TK
At April 2023 ToyKeeper made a multichannel version of Andùril 2
It starts at revision number 700
Rev. 710 (2023-05-03)
https://code.launchpad.net/~toykeeper/flashlight-firmware/multi-channel
→ post-off voltage display
→ UI change for multichannel

Thank you @ToyKepper for all the work!