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….
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
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.
The same on all lights? No, the ramp values are different for each build target. The ramp values shown in the manual are only examples.
Equally spaced? Yes, sort of. It’s equally spaced in terms of ramp steps… but what that means in lumens depends on the ramp shape. There’s a tool called steps.py which can be used to calculate exactly which ramp steps it’ll use. For example:
About what manufacturers publish, I’m sure we’d all like it if flashlight companies would consistently publish accurate data about their lights… but that problem is way beyond anything I can fix.
Thanks for the quick reply. I was hoping that something would remove the guesswork at approximating the lumen output at each step, other than referring to published reviews, or buying an integrated sphere.
I don't bother. Just pick a similar driver and overall "heat index" of the light. I don't recall what the A6 driver is exactly - 2 channels or FET+1. If FET+1, then use a Q8 or D4 config setting.
I've just received my first light with the Anduril UI (an Emisar D4v2 with Nichia E21A LED).
I have read in details the Anduril manual, many thanks and congratulations to ToyKeeper for this incredibly versatile and powerful UI, and for the detailed manual and useful diagram.
I have set my light to the stepped ramping, with only 5 steps because I like flashlights with few brightness levels.
Moreover, in order to have a very low Low, I set the Floor level to 2/150. Thus I have a real moonlight mode, nice for night bathroom trips. But I have noticed that when turning the light on in moonlight mode (1 Hold) the LEDs do not light up immediately, but only after about one second. This makes me keep the switch depressed longer than I should, and the light goes to Level2, which is much brighter than moonlight and blinds me. Hence my questions:
Is this one-second delay normal (see other issue below)?
Is there any way to reduce the brightness difference between Level1 and Level2? I assume that increasing the number of steps would automatically allow this, but as said earlier I don't want too many steps.
On the other hand, I notice that when a battery check (3C) says 3.7V, both my Fluke multimeter and my Opus BT-C100 charger say 3.85V. Can the battery voltage measurement be calibrated?
Now a strange behaviour of the lowest level: if the light has been in one of the highest modes, and I ramp down (click, hold) to Level1 (Floor level), the LEDs turn completely off. But the light is not OFF: in fact the LEDs do light up at the Floor level, but only after being completely off for 15 to 30 seconds! The warmer the light, the longer this delay: 15s when the light is almost cool (High for a short time), 30s when the light is extremely hot (one minute on Turbo).
Both of my KR4s exhibit the same behaviour, it isn’t a fault. It is a limitation of the driver type which the vastly more knowledgeable Toykeeper has better explained before. By default the bottom of the ramp (smooth, not stepped) is set to 3 due to the driver.
I set mine to 2 around the house and back to the default level 3 on night time dog walks.