ANDURIL USER MANUAL & LIST OF LIGHTS

Are you claiming that because the UI is similar, parts of the Anduril code must have been used? Do you have evidence beyond superficial similarity? Stepless ramping UIs had been independently developed and used in flashlights for years before Anduril (or its predecessor Narsil) were created. It’s more likely that Sofirn’s ramping UI as used in the Wurkkos FC11 and SP36S was developed from their own ramping UI as used first in the Thorfire TK18.

Anyone? I’m looking for some “bigger” MCU then Attiny85 supported by Anduril.
I tried to look through the FW repository, but there is so much versions and the orientation isn’t easy…
BTW files in this repository gives me “404” error: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/files/481/ToyKeeper/spaghetti-monster
EDIT: After some try I was able to get the FW as tar. After digging in the hwdef files I found Attiny 1634.

So far, just the attiny25/45/85 and attiny1634. I started adding attiny841 support too, but that project got cancelled. There’s also some very recent tinyAVR 1-series support too, added by gchart, but I haven’t merged it in yet.

I created and published the product map:

It’s not complete, but I think it’s a good start. Corrections / additions / patches are welcome.

I always liked the bike flasher but with Anduril for which you can adjust its brightness, at max brightness for example, the effect is less noticeable than at medium brightness, so instead of using the bike flasher, I’m using the tactical strobe at its lowest speed but I find it too fast (I’m using a FW3A with a red filter as a rear light).

Would it be possible to have a speed for the tactical strobe down to 1 flash/sec and an adjustment to the effect of the bike flasher along the ramping brightness, please ?

@ToyKeeper
Can I have the diagram in word or excel so that I make my one marks to understand it?

@uluNote10Plus
It’s in SVG format and you can find it here: ~toykeeper/flashlight-firmware/fsm : contents of ToyKeeper/spaghetti-monster/anduril/anduril.svg at revision 490

The bike algorithm is very simple… it runs at level N, and the pulses run at level 2*N. So, if it’s set to level 40/150, the pulses flash at level 80/150. However, it doesn’t limit the brightness to halfway up the ramp. It doesn’t stop at 75/150. The default allows it to go up to 120/150.

So it should then pulse at level 240, but there is no such thing. The light itself can only go up to 150.

In other words, no, I can’t make it brighter to make the effect more noticeable. It’s already going as bright as it physically can. If you want the pulses to be more visible, you’ll instead need to turn the brightness down. Like, instead of running at 120/150, maybe try turning it down to 90/150. Either way, it’ll pulse at 150/150, but that will look more noticeable when the base level is lower.

That … may be a bit excessive. Tail lights are usually not thousands of lumens. It’s likely to anger people behind you.

Have you considered using beacon instead? It has adjustable brightness and can run at 1 Hz…

Just bought sofirn sp36 anduril version and i’d like to use strobe cycles as momentary. Tried to power off while in strobe and 5C power on. Not working, did i miss something? Or maybe this light use an older anduril version? Any way to upgrade it to a newer firmware? Thanks for any input…

SP36 Anduril, as of the current time, still uses an older version of Anduril, without the momentary strobes modes.
(the same old Anduril version appears to be used by the Sofirn IF25A, Astrolux EC01 and Astrolux EC03).

I believe the SP36 Anduril can be updated to a newer version, and there is a pre-built hex file for it in TK’s repository, but my problem is I don’t think I can easily remove the driver (there are various tips & tricks mentioned in another thread here in BLF on how to remove the driver, but I think it’s bit beyond my skill level — I might break things and might not have the skill to fix them up).

Yeah… last I heard, the SP36 mostly ships with really old firmware. And it’s not easy at all to update, because they used very strong glue.

But Barry tells me sofirn has been working on updating the firmware and, someday, maybe even using different builds for different lights.

Curiously the Sofirn webpage for their new "SC31 Pro" states the following:

https://sofirnlight.com/sc31pro-2000-lumen-with-battery-p0134.html

I purchased two "SP36 BLF Anduril" lights this year from Amazon US in February and March that do not support the "15 or more clicks from off" Anduril firmware query. They also both have issues while in Muggle mode where they frequently ramp down to minimum brightness unexpectedly.

My Sofirn "Q8 BLF Anduril" light purchased this year from Amazon US in June returns a version date of "2019-09-28" from the firmware query and Muggle mode functions well.

My two Sofirn "LT1" lanterns (both with the newer "Rev. 5.0" driver board) purchased this year from Amazon US in June return a version date of "2019-11-29" from the firmware query.

Thanks for the info! The initial SP36 version was from late 2018, a version I sent as an early proof of concept but never intended for production. It was rejected at the time, so I didn’t think about it again until a user reported problems… We did some tests to determine the version, and the result was disheartening. So I bugged sofirn about it, and they started using newer versions.

Hopefully they’ll update everything to Anduril 2 when it’s ready. I mostly just need to finish the documentation.

I do agree and need to do more testing with someone else on my bike to better evaluate the possible nuisance for others but I’m using a bicycle rear light as my main red light and the FW3A with the red filter is pointed down to illuminate the bike frame in order to be better seen at crossroads by cars coming form left and right.

Yes since a couple of weeks when I realized by reading one of your message that the beacon was using the memorized ramp level. I tested beacon before, but as I generally don’t need a lot of brightness, the beacon was pretty dim. :person_facepalming:

All Right! Thanks for the info! I’m new to this and this is my first Anduril Flashlight. I love it! This UI should come with all the flashlights!!! I guess eventually, next generation flashlight will be updated via the usb port! I’ll keep an Eye on future version of sp36 and newer firmware since momentary strobe is an important feature for me….

The firmware of Lumintop HL3A is the same of the FW3A? I think so but I wanted to confirm it.

Could you tell me what is the rewind speed of the discrete modes in the Lumintop EDC18?
I wanted to understand how quickly the modes change when the button is held down. 0.5sec … 0.7sec

Original batch FW3A w/ SST20s:

How many clicks to set the ceiling to be at 100% duty cycle on the 8 7135s?

The FW3A firmware has the max regulated level at ramp step 130 of 150… so 21 clicks.

As far as I’ve heard, yes.

To help with figuring out this sort of thing, I created a product and firmware map called PRODUCTS. Also, in Anduril2, the version check function includes the build date and vendor/product ID to identify which exact firmware was used. So in the future it should be easier to get this info.

If I recall correctly, it’s one HOLD_TIMEOUT unit of time per step, and the firmware for that used a HOLD_TIMEOUT of 24 frames. Each frame is 16ms, so that’s 0.384s per step.

I see in the Anduril manual that the default stepped ramp is 7 steps between “floor” 20/150 and “ceiling” 120/150 (+ turbo).
Is this default setting the same on all Anduril lights? And are the 7 steps equally spaced?
Also, it would be great if manufacturers using Anduril could publish the expected brightness of each of the steps, as per “traditional” flashlights.