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

Do you know at what temp about it stabilized at?

For testing purposes, I set the limit intentionally pretty low. I was aiming for a stable level of about 200-400 lumens, and … that’s what I got. I think I told it that the ambient temperature was 20 C, and set the limit to 43 C, but I don’t remember exactly.

I wanted it to exceed the limit pretty easily and then step down somewhere slightly above the 1x7135 level. I could have set the limit much higher, but that makes the regulation problem easier to solve… and I wanted to see how it behaved on a harder setting.

Next I need to do full FET testing, since it’s the next step up in difficulty.

Looks like it worked as intended. Be interesting to see what it would do around 55c limit. What can the components tolerate? Typically up around 100c right?

I expect that turbo will overshoot the temperature limit before the light can settle to a stable level, so I wouldn’t put the limit too close to the hardware’s maximum tolerance.

The thermal sensor is inside the tiny85, which doesn’t have a great thermal path to the emitters. The measurements lag behind by quite a bit, so the response is lagged too. It tries to compensate for this by guessing where the temperature will be in the future, but that doesn’t entirely eliminate the problem. So the actual temperature goes higher than the limit at first, if the power is turned up high enough.

The firmware won’t allow a limit higher than 70 C… but it lets the user calibrate the sensor, so it’s not very hard to bypass that limit.

On a related note, that could potentially save a bunch of button presses while configuring things. If you tell it room temperature is 1 click (1 C), and then set the limit to only 1 click (30 C + 1), it’ll effectively have the same results as if you set room temperature to 20 C and the limit to 50 C. But the tempcheck mode will display numbers about 20 C too low.

I do not see him registered

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

Updated list : … Post moved to Page 130 , FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #3870 by pepinfaxera

Short list, Last requests .
.
.
.

I do not see him registered
.

Add me to the list please

I’d like it to blink on C

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.

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

Could you register my interest for 2 units please?

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

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

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”.

Sorry to make things difficult :disappointed:

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

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?

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.