DB_Custom
(Dale)
August 23, 2017, 8:50pm
1151
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
JasonWW
(JasonWW)
August 23, 2017, 9:12pm
1154
Unprotected cells only, due to length. That’s the only question I can answer for sure.
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
The_Miller
(The Miller)
August 23, 2017, 9:44pm
1157
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.
Rah_BE
(Rah_BE)
August 24, 2017, 1:42am
1158
Thanks. I like what you all are doing here.
Tixx
(Tixx)
August 25, 2017, 4:34pm
1159
Glad to hear the news about the manufacturing! This will be a cool light!
The_Miller
(The Miller)
August 25, 2017, 6:47pm
1160
Thanks.
Yeah a cool little hot running light but Narsil is very useful in finding a brightness level that does not overheat things
Joat
(Joat)
August 26, 2017, 5:54am
1161
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.
Joat
(Joat)
August 26, 2017, 5:58am
1162
ToyKeeper:
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:
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.
I should have posted a link here years ago when he first wrote that.
I still have his mailing address, got something good you would like me to forward to him?
joechina
(joechina)
August 26, 2017, 10:16am
1163
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?
patmurris
(patmurris)
August 26, 2017, 1:54pm
1164
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:
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 fro…
patmurris:
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?
joechina
(joechina)
August 26, 2017, 2:08pm
1165
Narsil, latest iteration is NarsilM, has a thread:
Release v1.3:
Here's the latest NarsilM v1.3 files: https://drive.google.com NarsilM v1.3
You will find a readme.txt file listing the .HEX pre-configured files there.
Please note v1.3 has no changes to the UI, therefore earlier manual revs still apply. Here's the revision history for v1.3:
Vers 1.3 2018-08-11:
- make SaveConfig() safer by disabling ints, ensure 0xff's get written in old position, using library routine first
eeprom writes and not using eeprom erase
- limit mode…
patmurris:
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: TK's Emisar D4 review - #1259 by patmurris
patmurris:
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.
The_Miller
(The Miller)
August 26, 2017, 3:47pm
1167
joechina:
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?
Well yes Narsil needs some tweaking for this small light and modes for the 7135 chips are high on my wish list for sure
g_damian
(g_damian)
August 26, 2017, 5:34pm
1168
Please add me to the list. Thank you.
The_Miller
(The Miller)
August 26, 2017, 5:40pm
1169
Welcome to BLF!
Yes will update list later
joechina:
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.
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.