Oh, um, before anyone asks… the “tint toggle” and “tint ramp” firmwares are not going to be merged into a single runtime-selectable option any time soon. They use totally different code, and the toggle method uses a bunch of custom overrides which aren’t compatible with anything else. These two don’t even use the same hwdef file. The differences between them are deeper than it might seem.
Here is a very quick component placement for a dual linear driver (no tracing, no layout optimizations)
Plus as bonus, dual current sense for a 1 000 000:1 dimming range (i.e. super low moonlight), which would also solves this :
That is if HDR/dual sense is supported, and supported for tint ramping (which looks like it would need a lot of changes to the tint ramping code).
Alternatively two small FETs + resistor channels could be used, that means supporting 4 total channels and 2 channels per LED tint ramping.
Anyhow putting the high dimming range aside, it would have 8 components on the back, only one more than the D4V2.5 driver. In term of cost, probably similar or if more, not by much : smaller cheaper linear FETs since only 2 LEDs per channels, no DD FET, since the 2 linear channels should be capable of close to direct drive performance. The op-amps being the most expensive parts, doubled, but slightly less precise and cheaper ones than in the D4V2.5 can be used if dual sense or resistor channels are used since thoses give much more dimming range.
I doubt it. I’m not sure, but I think the KR1 driver’s regulated circuit only goes down to 5A as the lowest turbo level. This is fine for the W1/W2 LED options, and for XP-L and SST-20… but Nichia 219B can’t really handle that much power. It’s rated for 1.5A and really should be kept at 3A or less. So Hank would need to make a lower-powered driver for it, or use special firmware which never goes above 50% or maybe 60% power.
For some lights, that’s worth doing… But in a thrower, 219B doesn’t really make much sense.
Yeah. I don’t know much about it, but it sounds interesting. I sent him a quick test firmware just to help verify if the driver works, and to check if I’ve got the right pinouts… but I haven’t heard any more details yet. Just some initial hardware-enablement type stuff.
Meanwhile, I’ve been enjoying a KR1 W1 in 18350 form. It’s small enough to lose in my purse until I need it, and throws way farther than such a small light seems like it should be capable of. I leave it in lockout mode, with a manual memory level set somewhere practical, so I can just pull it out and use 2H for momentary at a useful brightness. The beam is similar to an Emisar D1S, but the light itself is only a fraction of the size.