FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public

Nice! It will be manipulated according the user’s will! :+1:

I suppose that Crescendo is the case you mentioned. I’ve been using it (and like it a lot!!! Thanks TK!!) in a modded light but the auto-reversing is a bit “awkward” specially comparing witrh the Emisar D4 UI. It takes longer to get used to.

This said, I guess that sometimes it is harder to see when the top is reached, not the bottom. And that was the reason why I posted C and D as my options. The highest luminosity seems harder to control or to “eye-measure” than the lowest.

I still think that the blinks make sense to avoid pressing the button like there was no tomorrow and to mark some points while ramping.

This might be the only thing why I wold add the B mark, to know what to expect in terms of battery, as the highest regulation surely implies more drain than the 1st 7135 limit.

Still, so far I maintain my suggestion C and D.


Also, I have one question. Would the passage from full regulation to FET work as in the Emisar D4, meaning: after passinf that limit, and depending on the use LEDs that will be used, is it probable to see a “tint shift”? I have the D4 with XP-G2 S4 3D and I experience that “shift”. Don’t know how others react, and also don’t know it is supposed to expect that change on the new setting, after the regulation passage.

Please ignore my question if it is nonsense :innocent: And thanks again for the work done so far.

I want all blinks.
A
B
C
D

What I find interesting from the runtime table:
You gain 2h runtime if you go from 65 down to 62

Can we have the default level for power on set to level 62, please?

I dont think someone see a difference between 142 and 160 lumen and the 2h more seems to be a good trade-off.

Optical programming seems the most promising. But a lot of work and time.
I want that in a later premium edition of the FW3A with 90 CRI Nichia LEDs :slight_smile: not now

A sunrise mode, please no. I think it’s to hard to set with the lamp. And the µC cant sleep.

Leave room, it’s already feature packed.

Optical programming seems amazing!

@TK
one thing for the flow chart:
If you print it on a b/w laser printer you can’t distinguish the green and black lines very well.

Mabye if they are fatter?

A direct label on the lines maybe work
—x1—>
—h—>
—x1+h—>

mayby other lines
..-
—…—…—

Yes, but the effect isn’t as pronounced. This shows roughly what kind of tint shift to expect on three types of drivers.

With more digits shown, it’s not such a big difference:
62: 9.52 hours

65: 8.45 hours

The script rounded to the nearest integer, since the values are all approximate anyway.

Please add my name to the "interested" list for one light (first request).

Hmm, I’ll keep that in mind in case the diagram ships with the light. For now though, the .svg file is in the repository, and should work in Inkscape (free, runs on several OSes).

Do we have a current photo of the external design as of now?

Target production date or release date?

Not sure I’m familiar with negative voting. Can you just run raw numbers of for an option next to it? Also if people cannot stop at B and C, what will it accomplish? And force stopping would not be desirable I don’t think.

Hi. I would like to be put on the list for 1. Thanks

Those abilities seem cool. Getting to look like a custom guppy driver custom output settings like

I think people have forgotten that you can ramp both upward and downward. As you ramp down, you see the blink and you release the button. Done.

True, so you have to either pass it from low to high and stop and ramp back down or start ramping from above.

Put me on the list for one please.

I’m interested for 1 piece, so please put me on the list.

Using my D4, I don’t feel it has to be perfectly on the blink. I like the reference point because the human eye is terrible at judging brightness-

I frequently can’t tell if my Skilhunt H03 (last mode memory) is on medium (70lm) or high (160lm) until I cycle through the modes. The difference in modes is 10hours vs 5 hours runtime.

Nope, not yet.

As far as missing the channel blink, it could be programmed to stop there instead of just blink, then a new press would continue on in the ramp. But then, that would interrupt the ramp and all sorts of other issue. I don’t mind passing it going up then getting close coming back down, it means the lights output is just shy of maxed out on the 7135 chip so regulation is good. Stopping just over the blink of course has the FET engaged and you’ve entered into not-so-efficient territory. AS IF this were critical. In critical situations a spare cell should be readily available anyway, right?

So, I like the blink top and bottom, and the blink at the channel change. Where in the soup does that put my preference? :wink: