Interesting, Chrome and Edge don't show the pics, but Firefox does.
When did BLF switch to https ?
It’s in the anduril2 branch in Launchpad, or in my anduril2 file dump. It’s pretty much always a work in progress though, so use at your own risk.
Anyway, I got some test results from a wider variety of lights… and I’m seeing jump-start levels anywhere from 21 to 50 depending on the exact hardware being used. So it’ll probably take some tweaking on a per-light basis, for people who care to configure it.
That’s added and working now. The user can finally choose their turbo style, with different settings for simple and advanced modes. The available styles are:
- 0: no turbo, only ceiling
- 1: Anduril 1 style (Ramp 2H -> full power)
- 2: Anduril 2 style (Ramp 2H -> ceiling, unless already ramped up to ceiling)
This also controls the level of the momentary turbo shortcuts.
Turbo style is the 4th item in the ramp extras menu, or in the simple UI menu.
Some other new options were just added too, so some menus have changed…
Smooth ramp: (Smooth ramp 7H)
- Floor
- Ceiling
- Speed (new)
Ramp extras: (Ramp 10H)
- Automatic memory
- Manual memory timer
- Ramp after moon? (Off -> 1H) (new)
- Advanced UI turbo style (new)
Simple UI menu: (Off 10H)
- Floor
- Ceiling
- Steps
- Simple UI turbo style (new)
Hopefully this will let each person get the style they like.
Thank you TK. That is a wonderful addition! Anduril2 has become perfect in my eyes, with the latest work you have put in it!
Looking forward to someone updating the cheat sheets 
Putting the UI into a diagram is … harder than it was before.
Lux-Perpetua should be able to add/update the UI diagrams. He's got several versions for a variety of Anduril 2 configurations.
See: https://budgetlightforum.com/t/-/65927. I just added a post there.
Indeed it is, but some talented individuals have risen to the task admirably and have produced some very helpful diagrams. I hope they can include the latest improvements.
This is excellent! Thanks for all the work you’re doing.
I’ve been testing this with my E21A D4V2 and it’s been great, ultralow is so much more convenient now and makes the light more useful for me. Output appears more stable and startup is quicker. I especially love the ability to enable/disable ramp after moon activation, that’s a huge one for me.
I don’t quite understand though, how does exactly does the ramp speed configuration work? How many values are available? I only tried it up to about 20 clicks, which was maddeningly slow. What does each click represent exactly?
Also sorry dumb question but I am wondering, which hex would I flash to the DT8? I have both a 219b and a W2, do I just flash the respective KR4/KR4-219b versions?
The control chip has a timer which ticks at about 62 “frames” per second — one tick every 16ms. It’s pretty close to the speed of a common video screen. Normally, the ramp moves at one ramp step per frame, and there are 150 ramp steps, so it takes about 2.4s to ramp from end to end.
The ramp speed option changes it to one ramp step every N frames. So it slows things down… one step every 2 frames, every 3 frames, every 4, etc. Doing N clicks in the config makes the ramp 1/Nth as fast.
For reflashing a DT8, the readme file in my .hex file collection explains how to determine which file to use. The models file will probably be useful too. Basically, match up the model number.
Is there a way to add adjustable/more brightness levels for the AUX leds? I agree with a statement by ToyKeeper I saw on Youtube. The low setting is too low and the high is too high.
Nope, not without changing the hardware. The hardware only has three brightness levels:
- High
- Low
- Off
The way it produces those levels is by turning power on and off, and by inserting and removing a resistor along the path of current. The control chip provides the power, and it can either do that directly or it can add its internal resistor.
- High = power on, internal resistor off
- Low = power on, internal resistor on
- Off = power off
Those are the only three levels available.
The high mode’s brightness can be modified by changing the resistors on the aux board, or by replacing the resistors with potentiometers… but that’s pretty much the whole extent of the ways it can be adjusted.
Is this the same with button led brightness on d4v2?
O.K. thanks for the info. :+1:
Yes, it uses exactly the same mechanism.
The upside is, it’s completely passive so it can run for a very long time. Low mode lasts for years.
The downside is, it isn’t adjustable.
TK, is the dynamic PWM only implemented for the KR4 driver? I would love to be able to get lower lows on the Lume1 driver and on the FWAA driver.
pol77, in post #30, BurningPlayD0h mentions using the new code in a KR4.
I know it is used in the KR4. I was asking and it provides more granularity in the low modes and lower low modes. I was wondering if it is incorporated and can do the same for the other drivers, like Lume1 and FWAA.
Lume1 lowest modes are limited by the hardware.
Smoother ramp at the lower end, yes.
What about the FWAA?