The FW3A a TLF BLF special elegant triple powerful flashlight

4874 posts / 0 new
Last post
pepinfaxera
Offline
Last seen: 2 hours 31 min ago
Joined: 06/25/2015 - 12:53
Posts: 225
Location: Gijón - Spain - Europe

Agro wrote:
ABCD for me.

I do not see him registered

Sorry for my bad English
(google translator)

thebaum
Offline
Last seen: 2 months 4 weeks ago
Joined: 07/14/2014 - 19:54
Posts: 18
Location: texas

In for one

pepinfaxera
Offline
Last seen: 2 hours 31 min ago
Joined: 06/25/2015 - 12:53
Posts: 225
Location: Gijón - Spain - Europe

thebaum wrote:
In for one

Your name is already there nº 332 from The Miller list

A second unit?

Your name is already there nº 332 and 999

Sorry for my bad English
(google translator)

pepinfaxera
Offline
Last seen: 2 hours 31 min ago
Joined: 06/25/2015 - 12:53
Posts: 225
Location: Gijón - Spain - Europe

Updated list : … Post moved to Page 130 , http://budgetlightforum.com/comment/1337438#comment-1337438

Short list, Last requests .
.
.
.

Sorry for my bad English
(google translator)

pepinfaxera
Offline
Last seen: 2 hours 31 min ago
Joined: 06/25/2015 - 12:53
Posts: 225
Location: Gijón - Spain - Europe
Meyer wrote:
gi.lumens wrote:
The B/C option sounds reasonable,…
For me B/C too.

I do not see him registered
.

Sorry for my bad English
(google translator)

Calaveras
Offline
Last seen: 1 hour 42 min ago
Joined: 12/08/2017 - 19:25
Posts: 86
Location: California Gold Country

Add me to the list please

Spiderlight
Offline
Last seen: 3 weeks 5 days ago
Joined: 12/24/2017 - 19:17
Posts: 59
Location: Germany

ToyKeeper wrote:
  • A. Floor
  • B. ~150 lm, level 65/150
  • C. ~1000 lm, level 130/150 (highest regulated level)
  • D. Ceiling

I’d like it to blink on C
electricjelly
electricjelly's picture
Offline
Last seen: 3 days 13 hours ago
Joined: 08/23/2012 - 03:39
Posts: 443
Location: Los Angeles

ToyKeeper wrote:

So… which of the following reference points should blink when the user hits or passes them?
  • A. Floor
  • B. ~150 lm, level 65/150
  • C. ~1000 lm, level 130/150 (highest regulated level)
  • D. Ceiling

I vote for all A, B, C, and D.

I find the blinks very useful and not obtrusive at all.

There seems to be a lot of differing opinions about the blinks. Would it be feasible to have toggles for the various blinks in settings?

Thanks for all your attention to detail. This UI is looking amazing.

Eraursls1984
Offline
Last seen: 6 hours 16 min ago
Joined: 11/08/2014 - 01:44
Posts: 137
Location: North Florida

I think that the C blink should be before the end of regulation so we have time to stop while still in regulation.

Rusty
Offline
Last seen: 6 hours 56 sec ago
Joined: 04/11/2011 - 16:38
Posts: 25
Location: UK

Could you register my interest for 2 units please?

Persechini
Persechini's picture
Offline
Last seen: 2 hours 44 min ago
Joined: 07/11/2017 - 03:32
Posts: 503
Location: Brasil

I’ve made my mind, I’m in for one unit

In my Tree

My collectionEmisar: D4 / D1 / D4 (broken) ― Convoy: C8 Clear / S2+ Clear / S2+ / S2+ UV / S6 ― Nitecore: Tube / Thumb / Concept 1 / HC30 / HC33 / TIP / TIP CRI / TINI ― Lumintop: Tool AAA / Tool AA / HLAAA / EDC05 ― Sofirn: SF10 / SF12 / SF12 / SF14 / SF14 / SF14 / SP10A / SP10A (gifted) ― Jaxman: E3 ― UTorch: UT01 ― Trustfire: Z2 ― Skyfire: SF-065 (trashed)

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3
pepinfaxera wrote:
I do not see him registered

Hmm. Do you think votes should be limited only to people who are on the interest list?

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3

Blink option running vote tally…

As a reminder, the options are: (where in the ramp to blink)

  • A. Floor
  • B. ~150 lm, level 65/150
  • C. ~1000 lm, level 130/150 (highest regulated level)
  • D. Ceiling

Totals:

  • A: -7
  • B: 3
  • C: 14
  • D: 3

19 votes:

I’ve been saving each vote as sort of a trinary variant of Approval voting… capital letter for +1 point, lower-case letter for +0, letter omitted entirely for -1. Originally I had planned on doing regular Approval voting, but Pulsar expressed a lukewarm opinion about option C so I added a state between “approve” and “disapprove”.

Pulsar
Pulsar's picture
Offline
Last seen: 2 months 4 weeks ago
Joined: 07/29/2011 - 00:41
Posts: 5834
Location: Maine

Sorry to make things difficult Ughh

Eidt: I am surprised to see the results on blink A though

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3
electricjelly wrote:
There seems to be a lot of differing opinions about the blinks. Would it be feasible to have toggles for the various blinks in settings?

Maybe, but it’d add UI complexity that I’m not sure is worthwhile. The ROM is also getting close to full, so I’ve been a bit picky about what I add. I’m hoping it can be decided by vote instead of using most of the remaining space for ramp blink options.

Other things that space could potentially be used for:

  • Make ramp memory optional? (always turn on at same brightness)
  • Add a sunrise / alarm clock mode?
  • Make muggle mode fancier? (simplified ramping or low/med/high or something)
  • Factory reset function?
  • Add another “mood” or blinky mode?
  • Optical programming mode? (configure the light from a web page, like a Lux-RC driver)
  • Leave room for enabling non-default compile-time options, like dual-switch support?
  • Leave room for other people’s mods?
ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3
Pulsar wrote:
Sorry to make things difficult Ughh

If I give it weights of (1, 0.5, 0) instead of (1, 0, -1), things might look a bit different:

  • A: 6.0
  • B: 11.0
  • C: 16.5
  • D: 11.0

Or if those are expressed as a percent of total votes:

  • A: 31.6%
  • B: 57.9%
  • C: 86.8%
  • D: 57.9%

Perhaps it’d be best to use the percent, and set a threshold for what’s high enough. Like 50% or 66%, maybe. The positive/negative weighting kinda implies a threshold of 50%, but that might not be ideal.

pepinfaxera
Offline
Last seen: 2 hours 31 min ago
Joined: 06/25/2015 - 12:53
Posts: 225
Location: Gijón - Spain - Europe
ToyKeeper wrote:
pepinfaxera wrote:
I do not see him registered
Hmm. Do you think votes should be limited only to people who are on the interest list?
Oh do not,

Just warn not to close the purchase group and stay out.
. -
. -

Edit: Do not be this what I want to say

Google translator error
. –

Sorry for my bad English
(google translator)

Tender
Offline
Last seen: 6 months 1 week ago
Joined: 09/15/2017 - 02:26
Posts: 138
Location: NY, NY

I would say only add those blinkies that are functional. You mentioned that the pause at B and C are too quick for anyone to respond to stop ramping from going beyond regulation (when ramping up). Therefore I would say it is not functional in the sense that you can actually do something with it, (although it does provide information, there isn’t something you can do about it in the moment. You would have to stop ramping up, and start ramping back down, and stop slightly lower than regulation). Whereas A and D give you a definite indicator – we’ve reached our destination, (programmed or otherwise) – you can now release the button.

You could just program a function that will set the light to the different regulations. It could be another mode, but I would rather have some of the fun functions you outlined above. I like:
“Add a sunrise / alarm clock mode?
Make muggle mode fancier? (simplified ramping or low/med/high or something)”

I vote for A and D

"Keep On Luxing" © and "May The Lumin Be With You" © (by my very self)

themaindude
Offline
Last seen: 5 days 3 hours ago
Joined: 09/27/2011 - 21:31
Posts: 88
Location: Philadelphia Suburbs

Can you place me on the list for 2 please.

barrybluejeans
Offline
Last seen: 2 weeks 1 day ago
Joined: 12/22/2017 - 11:11
Posts: 38
Location: United States

in for 1, thanks

WTB ArmyTek Prime C1 body tube only, cree 1A xpl led, single TIR reflectors

gravelmonkey
Offline
Last seen: 4 hours 47 min ago
Joined: 08/17/2012 - 20:28
Posts: 206
Location: UK/South America

A and D.

And I would be happy with either B or C, I normally top off my cells pretty regularly, a blink at either B or C would tell me I have 8hrs or 1hour runtime, respectively.

Weird, off the wall suggestion, would a “max brightness at runtime X” work?

Ie, in a config mode, select runtime required (one click per…half hour? So 5 cicks is 2 1/2 hours), light blinks clicks back as a verification of required time and goes to the brightest output the cell can sustain for that amount of time. A full cell will obviously output more lumens than a 1/2 full cell, but both would run for the same 2 1/2 hours.

I assume uncalibrated voltage measurements from the driver would make this unworkable though.

Lazy-R-us
Offline
Last seen: 8 hours 19 min ago
Joined: 09/13/2015 - 00:30
Posts: 674
Location: Carolinas, USA

I vote A and D, especially if auto reverse is implemented. The changes at the extremes are the most difficult to perceive, so I find it useful to know when to let go of the switch.

The mid blinks serve little purpose to me, as mentioned above the ramp rate is so high, it just tells you that you passed the point – like a mile marker that you can’t see until you pass it going 60.

Lazy-R-us

goshdogit
goshdogit's picture
Online
Last seen: 5 min 24 sec ago
Joined: 12/03/2015 - 21:28
Posts: 787

ToyKeeper wrote:
  • Make muggle mode fancier?
  • Add another “mood” or blinky mode?
  • Optical programming mode?
Ramping Muggle Mode sounds great.

Another “mood” mode? Tell us more! I love Candle Mode in Andúril.

Optical programming would be amazing. I remember you talking about it a while ago, and I’ve seen your video demonstrating it.

Back in the 90s, I played around with a Timex Datalink watch that had a similar data transfer feature. It still seems very high-tech! LOL

Eraursls1984
Offline
Last seen: 6 hours 16 min ago
Joined: 11/08/2014 - 01:44
Posts: 137
Location: North Florida

Edit: since it stops on the lowest mode, and highest regulated mode, I see no need for any blinks.

JasonWW
JasonWW's picture
Online
Last seen: 7 min 11 sec ago
Joined: 10/22/2016 - 11:41
Posts: 8297
Location: Houston Texas

Lazy-R-us wrote:

The mid blinks serve little purpose to me, as mentioned above the ramp rate is so high, it just tells you that you passed the point – like a mile marker that you can’t see until you pass it going 60.

Just ramp downward.

My Convoy L6 thread with XHP70.2, Texas Avenger FET driver, Narsil v1.2 ramping firmware (old), lighted side switch and cut down SMO reflector. Lots of amp draws on stock driver as well. 

My Supfire L5-S thread with XHP70.2, 26350 cells (4,100 lumen!), Texas Avenger FET driver, NarsilM v1.0 ramping firmware and lighted side switch. My mini L6! 

9 NarsilM user videos for BLF Q8, GT, GT Mini and ROT66

Texas_Ace BLF Calibrated Lumen tube

Maukka Calibration Lights for DIY Lumen Measuring Devices 

Review Jaxmnve M1 Stainless 10180 Keychain light

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3

The ramp stops at the top and bottom. To turn around, let go of the button and then hold it again.

The top/bottom blinks were initially added as part of an auto-reversing UI, but I’m not sure they make any sense in a UI which stops on its own. It’s not generally hard to tell that it has stopped, especially at the bottom end. However, it can be difficult to gauge how far up the ramp the light is. I configure mine with a blink at channel boundaries only. This lets me know if I should expect more than 8 hours of runtime, between 1 and 8 hours, or less than 1 hour.

None of the options should be an issue for anyone with firmware flashing tools, but I hope to make the default agreeable to as many people as possible. So far, it sounds like that means option C only, a blink at the highest regulated level before the FET kicks in. That also happens to be where the ceiling is set by default, which would mean it has a blink at the top of the ramp unless the user changes the ceiling level.

Since there’s also a configurable stepped ramp which can be used to consistently reach precise levels, I’m leaning toward relatively few blinks. Set your preferred floor, ceiling, and number of steps, and it’ll give you a mode with evenly-spaced levels (plus turbo, if not already in the ramp). For example:

  • 3 steps from 20 to 130: 11 / 240 / 1100 lm (plus turbo)
  • 4 steps from 10 to 130: 3.3 / 84 / 394 / 1100 lm (plus turbo)
  • 5 steps from 3 to 150: 0.8 / 47 / 246 / 741 / 3000 lm

It can be whatever you like.

Tender
Offline
Last seen: 6 months 1 week ago
Joined: 09/15/2017 - 02:26
Posts: 138
Location: NY, NY

ToyKeeper wrote:
The ramp stops at the top and bottom. To turn around, let go of the button and then hold it again.

The top/bottom blinks were initially added as part of an auto-reversing UI, but I’m not sure they make any sense in a UI which stops on its own. It’s not generally hard to tell that it has stopped, especially at the bottom end. However, it can be difficult to gauge how far up the ramp the light is. I configure mine with a blink at channel boundaries only. This lets me know if I should expect more than 8 hours of runtime, between 1 and 8 hours, or less than 1 hour.

None of the options should be an issue for anyone with firmware flashing tools, but I hope to make the default agreeable to as many people as possible. So far, it sounds like that means option C only, a blink at the highest regulated level before the FET kicks in. That also happens to be where the ceiling is set by default, which would mean it has a blink at the top of the ramp unless the user changes the ceiling level.

Since there’s also a configurable stepped ramp which can be used to consistently reach precise levels, I’m leaning toward relatively few blinks. Set your preferred floor, ceiling, and number of steps, and it’ll give you a mode with evenly-spaced levels (plus turbo, if not already in the ramp). For example:

  • 3 steps from 20 to 130: 11 / 240 / 1100 lm (plus turbo)
  • 4 steps from 10 to 130: 3.3 / 84 / 394 / 1100 lm (plus turbo)
  • 5 steps from 3 to 150: 0.8 / 47 / 246 / 741 / 3000 lm

It can be whatever you like.


I would definitely prefer to have ramping automatically stop at the set boundaries.

Now this makes a lot more sense: Since floor and ceiling can be programmed precisely, and likewise for various precise steps, it eliminates the need for blinks, other than when ramping is set to go beyond regulation and into FET.

So C informs about potential high power draw. I guess that can be helpful for people who are in a situation where they want/need to preserve runtime

"Keep On Luxing" © and "May The Lumin Be With You" © (by my very self)

Tender
Offline
Last seen: 6 months 1 week ago
Joined: 09/15/2017 - 02:26
Posts: 138
Location: NY, NY

ToyKeeper wrote:
The ramp stops at the top and bottom. To turn around, let go of the button and then hold it again.

The top/bottom blinks were initially added as part of an auto-reversing UI, but I’m not sure they make any sense in a UI which stops on its own. It’s not generally hard to tell that it has stopped, especially at the bottom end. However, it can be difficult to gauge how far up the ramp the light is. I configure mine with a blink at channel boundaries only. This lets me know if I should expect more than 8 hours of runtime, between 1 and 8 hours, or less than 1 hour.

None of the options should be an issue for anyone with firmware flashing tools, but I hope to make the default agreeable to as many people as possible. So far, it sounds like that means option C only, a blink at the highest regulated level before the FET kicks in. That also happens to be where the ceiling is set by default, which would mean it has a blink at the top of the ramp unless the user changes the ceiling level.

Since there’s also a configurable stepped ramp which can be used to consistently reach precise levels, I’m leaning toward relatively few blinks. Set your preferred floor, ceiling, and number of steps, and it’ll give you a mode with evenly-spaced levels (plus turbo, if not already in the ramp). For example:

  • 3 steps from 20 to 130: 11 / 240 / 1100 lm (plus turbo)
  • 4 steps from 10 to 130: 3.3 / 84 / 394 / 1100 lm (plus turbo)
  • 5 steps from 3 to 150: 0.8 / 47 / 246 / 741 / 3000 lm

It can be whatever you like.


I would definitely prefer to have ramping automatically stop at the set boundaries.

Now this makes a lot more sense: Since floor and ceiling can be programmed precisely, and likewise for various precise steps, it eliminates the need for blinks, other than when ramping is set to go beyond regulation and into FET.

So C informs about potential high power draw. I guess that can be helpful for people who are in a situation where they want/need to preserve runtime.

How do the steps work? Does it pause at each step?

"Keep On Luxing" © and "May The Lumin Be With You" © (by my very self)

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3
gravelmonkey wrote:
would a “max brightness at runtime X” work?

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 4×18650 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.

goshdogit wrote:
Ramping Muggle Mode sounds great.
Another “mood” mode? Tell us more! I love Candle Mode in Andúril.

Optical programming would be amazing.

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.

ToyKeeper
ToyKeeper's picture
Online
Last seen: 1 min 6 sec ago
Joined: 01/12/2013 - 14:40
Posts: 7873
Location: (469219) 2016 HO3
Tender wrote:
How do the steps work? Does it pause at each step?

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?

Pages