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

Beam0 I believe it ramps until you release button.

Now I have a question.

Does memory remember everything

I think it should remember what ever you were in last.

I’d be interested in one as well!

You are number No. #1109 on: Interest list , Post # 4 , Page 1 “:FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #4 by FW3A_Team
.
+1, I put it in the number #1176 on: ”Interest list updated by pepinfaxera, View page 71, “:FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #2127 by pepinfaxera ,
FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #2127 by pepinfaxera ,
For a total of 2 lights .

How many lanterns do you want in total? … x … units? .
.

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

-

It sounds like you got it in a later post, but I’ll try to answer all the questions at once.

The bottom dotted line in the ramp is the floor level. The top dotted line is the ceiling level. The middle dotted line is the 1x7135 level. Floor and ceiling are configurable.

  • Click from off: Memorized level. Defaults to 1x7135 after disconnecting power.
  • Hold from off: Floor level, then ramp up until button is released.
  • Double click from off: Ceiling level.
  • Click, release, hold from off: Ceiling level, then ramp down until button is released.

Ramping only happens when the button is held. If it ramps while not holding the button, something went wrong with the button connection, and the light should probably be loosened/tightened to reset the contact. I have seen this happen on occasion if the light gets knocked sideways and moves the position of the inner tube far enough to contact ground.

Depends on the pocket.

There isn’t currently a free pin to drive an indicator LED, since the pin it would normally use is allocated for the third main-emitter power channel instead. There is also no pad for a fourth LED on the MCPCB, nor room to route another wire there.

There is a compile-time option in Anduril for this. The default is set to the 1x7135 level or ~150 lm, which is about 3X as high as what the D4 firmware used. The regulation algorithm is also completely different.

#define MIN_THERM_STEPDOWN MAX_1x7135  // lowest value it'll step down to

It remembers almost everything, but when it’s off it is mostly stateless… ish. Like, if you were in candle mode when you shut it off, a single click will not return to candle mode. It’ll go to the regular ramp instead. But if you were in muggle mode when turning it off, it’ll return to muggle mode on the next click.

There are effectively four different “off” states:

  • Normal operating mode.
  • Soft lockout mode.
  • Momentary mode.
  • Muggle mode.

Most settings are remembered after a battery change. However, a battery change resets a few things:

  • Reset to normal operating mode, unless muggle mode was active. (cancels lockout and momentary)
  • Reset ramp level to 1x7135 (~150 lm).
  • Reset candle brightness to default.

A tiny locator led can be always on, it then does not need a pin, just a 10K resistor on the driver, and pads on the MCPCB. You can not use it to signal things then, and it can only be switched off with a mechanical lockout. The tiny led could also be at the tail (but there’s no hole there for the light coming out, it would be there but nobody ever sees it :open_mouth: ).

The optic nerve pin might also be usable to drive an indicator LED, if the sensing function was sacrificed. I haven’t checked the attiny docs to see if that pin has the relevant functions, but it probably does. And the optical programming stuff hasn’t been written yet.

I’ve kinda been waiting on the second prototype to arrive since I’ll have to mod the light to do any optical programming development on it, and it won’t be usable for non-development purposes any more.

Please put me down for 1!

Please, put me down for one.

kahvitahra should enter and publish how many lights he wants
.
In Interest List, Post # 4 Page 1, it only has one “1” .
2nd cancelled.
.

The right column, not the left column. :slight_smile:

Three posts: Two requests, one cancellation. Total of 1 light. Currently #809 on the list.

Because of the accidental second request, I used kahvitahra as a test case for the code which handles cancellations.

.
.
I apologize
My mistake
Now I have to edit Post 2128 and 2129 Page 71.
Sorry.
.

OK, TK does it remember the Last Blinky and the Last Strobe ??

What are the default Blinky and Strobe modes ? After a power cycle?

Sounds great.

It remembers the last-used mode in the strobe group. However, the blinkies always start at battcheck.

This can be partially inferred by the arrows from “off” in the diagram, since one points directly to battcheck and the other points only to the strobe group.

Great. i love it

please add 2 more for me for a total of 4. thanks

I’m liking this flashlight even more. I’m interested in getting a second one (my first one is #983).

There is a thread for drilled optics that can fit 3x tritium in your color choice that can serve this purpose. It’s quite a bit more expensive than your suggestion but it also glows with no drain on the battery.

I saw recently that Oveready is using optical programming on their Boss lights. I wonder if that stemmed from discussions on BLF or if they have berm doing it a while. They also use the same optical sensor as a safety feature against their light turning on in your pocket somehow and cooking your leg.

http://lux-rc.com makes their drop ins and they have been doing optical programming for a while, along with some other very advanced features.