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.
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).
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.
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?
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:
- Agro
- CRX
- Garth
- MascaratumB
- Meyer
- PBWilson
- Persechini
- Pulsar
- Spiderlight
- Tixx
- ToyKeeper
- Yammie
- electricjelly
- gi.lumens
- keengeorge
- mustig
- pepinfaxera
- skinny_tie
- varbos
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”.
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
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.
Those abilities seem cool. Getting to look like a custom guppy driver custom output settings like
Also if people cannot stop at B and C, what will it accomplish?
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.
Tixx:Also if people cannot stop at B and C, what will it accomplish?
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.
Do we have a current photo of the external design as of now?
Target production date or release date?
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?
Out of curiosity, I tried making the smooth ramp blink every time it passed a stepped ramp level. This would make the number and placement of blinks configurable… but in practice it was mostly just annoying. Then again, the default config had 7 steps.
Updated list : … Post moved to Page 111 . FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #3305 by pepinfaxera
Interest list … The Miller … pepinfaxera
—-
588 … darrylo
589 … darrylo 2nd
932 … darrylo 3nd …
933 … darrylo 4nd …
—-
246 … robbobus
941 … robbobus …
942 … robbobus …
—-
. 17 … Ozythemandias
411 … Ozythemandias
—-
289 … BeardedRaleigh
578 … BeardedRaleigh
943 … BeardedRaleigh …
944 … BeardedRaleigh …
—-
362 … Gj
413 … Gj
414 … Gj
415 … Gj
772 … Gj
—-
391 … shilent
773 … shilent
—-
…… … Agro … Edit: Not yet registered
—-
332 … thebaum
999 … thebaum … 2º nd?
—-
…… … Meyer … I do not see him registered
…… … TLF nº 221
—-
…… … khas … I do not see him registered
Post #1309
—-
Interest list
—-
See Poost # 182
Put me down for one please.
Any plans for a 18500 tube :innocent:
khas: The Miller has not included him in the list
See Post #1309
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.
I don’t like “traditional” style as muggle mode. So either “training wheels” or “dead simple”. I suppose “training wheels” should be simple enough to learn about after a few minutes usage, so I’d more likely go for “training wheels” muggle mode.
I would like to see blinks at A, C, and D. I like those blinks on my D4, and how I describe the brightness to people depends on the middle blink.
off
Sensible Bright
blink
Stupid Bright
blinding