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

That would be tricky. The voltage measurements arenā€™t very precise, and it has no idea what kind of battery is being used or how its discharge curve is shaped. Could be a 2500mAh 18650 with a sharp elbow in the discharge curve, could be a 3400mAh 18650 with barely any elbow at all, could be a 700mAh 18350 cell with a spacer or short tube, could be 4x18650 in parallel, could be something which isnā€™t invented yet. Iā€™ve been trying to avoid adding anything hardware-specific when possible since itā€™s intended to be portable across a wide range of drivers.

Iā€™m currently using FSM-based UIs on the entire range of Emisar lights, the FW3A, the BLF Q8, and a lightsaberā€¦ and plan to add BLF GT support as soon as I have hardware. Theyā€™re all running Anduril, except for the lightsaber, which has a fancy rainbow synthesizer UI instead.

Last time I asked, there wasnā€™t much consensus on how muggle mode should workā€¦ so I went with the simplest option. That can change, if people want it to. Some options:

  • Dead simple style: On/off only, ~150 lm. <ā€” current option
  • Traditional style: Low/med/high/off sequence, 10/80/300 lm.
  • Training wheels style: Simplified smooth ramp, 5 lm to 300 lm.

About another mood mode, I donā€™t have anything particular in mind. But if someone has a good idea, maybe it can happen.

Iā€™m not sure if thereā€™s enough space left for optical programming or not. Itā€™s definitely the most work out of the things I mentioned, and Iā€™d need to physically modify this FW3A prototype in order to do the development. Perhaps after the second prototype is made, I can turn the first one into a dedicated development host. For now though, I need it intact for thermal testing.

It works the same as the smooth ramp, except it only uses the configured steps, and each step is held for about 0.4 seconds. Itā€™s similar to an Olight Baton interface, plus the ability to go down instead of only up. If the button is held, it will keep ramping until the user lets go or until it hits the end of the ramp.

BTW, Iā€™m not clear on what your vote is now. It was AD, but now it sounds like maybe C or None?

I like option C also, as well as the dead simple muggle mode. Iā€™m not going to complain however it works out though.

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.