Yes will do!

The Miller, what does that mean for the q8? Is it to be put on the back burner until after the busy season?

Q8 is build by a different manufacturer, so there are no links between the two projects. Also, Q8 is afaik already in production (at least a first batch)

Legal 710 I understand all about that. The Miller made a post about it on the previous page so I thought it prudent to ask for clarification in the same thread. Thanks

Please add me to interest list. Thanks.

The Q8 is being made, but from both Thorfire and Lumintop it is clear seasonal production is a real factor, so this means I do not expect the FW3A of which the CADs are talked about can be done fast (unless of course LT sees it as a good addition for the busy Q4 but don’t don’t count on it, we want it right so rather a bit later

Add me to the interest list. Thanks.

Yes will do!
And welcome to BLF!

Please, i want one too. Thank you.

The 10511 has a solid surface as compared to the cup like indentation in the more common 10507. If you’re not using a glass lens to cover the optic, dirt and lint can gather in those insets in the 07.

This shot from Cutter shows it pretty clearly, the 10507 is in the back…

There is another week-long holiday (Golden Week) starting Oct. 1st that won’t help things (from our perspective, anyway).

I’ll take one.

Any idea of peak lumens? Usable constant lumens?

And any beamshots? I admittedly did not look through all 30+ pages.

Also this flashlight would likely require a high drain battery right?

Sorry for so many questions lol

Unprotected cells only, due to length. That’s the only question I can answer for sure.

DB Custom wrote:

The 10511 has a solid surface as compared to the cup like indentation in the more common 10507. If you’re not using a glass lens to cover the optic, dirt and lint can gather in those insets in the 07.

I have a lens over my 10507, and according to the specs the FW3A does too. But I’ve definitely had lights with a bare non-flat optic, and it gets annoying trying to keep it clean.

Please add me to the FW3A list. Thanks! Charlie

Welcome to BLF!

Hard to say max output and max long term output.

For the Q8 we kept on saying 4K lumens , we wrote 5K in the text for BG listing, yet with right cells it does more.

Here the same, for now we say 2500 lumens max but we do expect it to be a bit higher
Long sustained output, we can say more when more testing is done.

The Miller wrote:

Yes will do! And welcome to BLF!

Thanks. I like what you all are doing here.

Glad to hear the news about the manufacturing! This will be a cool light!

Tixx wrote:

Glad to hear the news about the manufacturing! This will be a cool light!

Please add me to the interest list, this is the first BLF light that might knock my modded EE A6 out of the running for my main EDC.

ToyKeeper wrote:

I have to laugh though… I googled “flashlight cult” and the first hit was an article about something I made. Why am I not surprised?

Here’s an excerpt:

A random BLF-A6 review wrote:

Holy crap, I don’t even deserve this flashlight! Almost timorously, I clicked the end cap again. Positively alarming things happened. I looked at the enclosed instructions…

[photo of one of my UI diagrams]
[Caption: Documentation Guy went off his meds today…]

… I will strive to be worthy.

So, that made my evening a little brighter.

BrianK wrote:

Interesting read. I wonder what he’d write regarding the latest BLF lights?

I still have his mailing address, got something good you would like me to forward to him?

Is there a chance that some of the new cool features of Toykeepers D4 firmware, e.g.

- default 100% of the 7135 at power up

are build in the FW3A?

Speaking about the UI and Narsil, i only recently experienced it with the Emisar D4 and have a few issues with it. I understand the D4 uses a stripped down version with ramping only and no other mode groups to chose from.

from:
http://budgetlightforum.com/comment/1168000#comment-1168000

patmurris wrote:

A few comments about the ramping UI:

I like how smooth and fast it reacts and that the current level stays in memory for the next turn on. However if i set the light to some mid level i like and next use the shortcut to moon for instance (long press from off) and turn the light off, the next time it will also start on moon with a single click – the memorized mid level has been ‘erased’ by moon, even though i didn’t use ramping. Same thing if i fired a quick burst of max output (double click from off) and turned off without ramping. Next time it turns on at max level which may be unexpected and quite annoying.

In both case, the memorized level was forgotten and one of the shortcut has become redundant. I would have expected the memory to persist until some ramping occur.

Another suggestion i would make would be to have an option to limit ramping to a level that the light can at least sustain for a few minutes without stepping down or becoming ridiculously (and possibly dangerously) hot. It’s actually too easy to go overboard with this light. On most lights with a turbo mode of some sort, you have to do something special to trigger it – at least click through the other modes for instance.

Maybe there is a better place to discuss Narsil?

patmurris wrote:

Maybe there is a better place to discuss Narsil?

Narsil, latest iteration is NarsilM, has a thread:
http://budgetlightforum.com/node/54635

patmurris wrote:

Speaking about the UI and Narsil, i only recently experienced it with the Emisar D4 and have a few issues with it. I understand the D4 uses a stripped down version with ramping only and no other mode groups to chose from. from: http://budgetlightforum.com/comment/1168000#comment-1168000

patmurris wrote:

A few comments about the ramping UI: I like how smooth and fast it reacts and that the current level stays in memory for the next turn on. However if i set the light to some mid level i like and next use the shortcut to moon for instance (long press from off) and turn the light off, the next time it will also start on moon with a single click - the memorized mid level has been 'erased' by moon, even though i didn't use ramping. Same thing if i fired a quick burst of max output (double click from off) and turned off without ramping. Next time it turns on at max level which may be unexpected and quite annoying. In both case, the memorized level was forgotten and one of the shortcut has become redundant. I would have expected the memory to persist until some ramping occur. Another suggestion i would make would be to have an option to limit ramping to a level that the light can at least sustain for a few minutes without stepping down or becoming ridiculously (and possibly dangerously) hot. It's actually too easy to go overboard with this light. On most lights with a turbo mode of some sort, you have to do something special to trigger it - at least click through the other modes for instance.

Maybe there is a better place to discuss Narsil?

Im nearly 100% positive that the regular Narsil M does just what you say. From off press and hold-ramp to some med output(leave on at least 1/2 sec)-click off(output memorized). Long press- to moon -click off. Quick click- back to the med output memorized mode. Double click from any mode except turbo- Turbo- click off. Quick click on-back to memorized mode.

After you've set the memorized mode, if you press and hold from off to get moonlight, you have to be sure to let go while at the lowest output, so pretty much you have to let go as soon as you see light or it will reset the memorized mode. This is with NarsilM. 

joechina wrote:

Is there a chance that some of the new cool features of Toykeepers D4 firmware, e.g.

- default 100% of the 7135 at power up

are build in the FW3A?

Please add me to the list. Thank you.

Welcome to BLF!
Yes will update list later

joechina wrote:

Is there a chance that some of the new cool features of Toykeepers D4 firmware, e.g.

- default 100% of the 7135 at power up

are build in the FW3A?

Depends, but I’m guessing probably yes.

patmurris wrote:

Speaking about the UI and Narsil, i only recently experienced it with the Emisar D4 and have a few issues with it.

If I recall correctly, Tom already implemented those memory suggestions. However, I’m not aware of any features to limit maximum output.

I’ve been pondering how to configure the lowest level; maybe I could also make something to configure the highest level. I’m doing a somewhat different interface though… instead of pre-defined mode groups, the user sets the number of modes and the brightness of the lowest mode. Perhaps they could also set the brightness of the highest mode. Afterward, the discrete ramping then has the selected number of evenly-spaced steps between the endpoints.

The upside here is that it’s simple, flexible, and always evenly-spaced. However, the downside is that it would be unlikely that any discrete levels would hit either of the sweet spots with a 7135 channel maxed out.

I’m also hoping to make it relatively easy to switch between smooth and discrete ramping, without a trip through config mode.

Just some thoughts for now. It’ll be more concrete later.

You’re being too hard on us TK! Give us a break!