New Basic UI (based on FSM/Anduril code) - do you like it?

New minor update:

  • removed that misplaced, obsolete arrow (sorry for that)
  • added 2H to directly ramp down in ramping mode (1:1 consistent to Andúril UI)
  • changed OP and thread title to be more precise what this thread is about

For now, I see following manufacturers/brands interested in this UI already:

Sofirn - Wurkkos - Yakorsei

WildTrail (ex LuckySun)

They may wanna try to build that firmware on their own (i.e. proprietary) but I see nothing but benefits to have this firmware coded in FSM, taking advantage of the Andúril code.

Maybe ToyKeeper or someone else experienced in GPL licensing can guide me through any obstacles that have to be taken care of in order to avoid any licensing issues? I tried to reach out to TK before (Andúril 2 UI chart) but did not get any response yet.

My 2¢ is that strobe beacon and sos are better served by bike strobe, battery check, and beacon.

I get a heap of customers who need strobe, but no one needs sos, most would think it’s just a blinky light in the distance lol. Bike strobe would be a good idea though

LEOs? Or Tacticool Joe’s? I am the type that carries extra equipment with me at times but I’ve never ever thought of a situation where strobe is my lifeline.

I don’t mean to downplay the market that exists for this function, as a ‘want’ is just as important as ‘need’ when selling a product. I just don’t know if I’ve ever known a person or situation that strobe is useful practically. Maybe in a SWAT raid…

Come to think of it, the people who ask me will usually pick up a tail clicky anyway.

I do think manufacturers will request it has strobe and sos since that’s is what is included 99% of the time.

Battery check on the button led is enough. I’ve never used the battery check function on every model that uses it. I can always tell by looking and charge cells before they get too low anyway. Most models that get this firmware will have usb charging and so it’s more likely people will chuck it on charge after a bit of use. This is also a simplified UI, so most users won’t know what 3 blinks and 7 blinks means, if they do then most have no idea that 2.5v is empty and 4.2v is full. 3-5 blinks representing an estimate is simple

I’m not going to care what the final result is though, as long as the UI is as seen above for ramping and stepped. I thought Anduril 2 was the answer until TK disabled the Turbo on the Simple UI

There’s a lot of users that aren’t noobs that wanted Anduril 2 to have the Simple UI with the normal Turbo. I’ve activated various settings in certain situations that made it frustrating to use. All I use is smooth ramping, stepped at times, with turbo, that’s it. Anduril 2 could use Turbo if you first configured the ceiling as 100%, but then what happens if you want to borrow the light to someone, you either have to configure it back or factory reset it and then spend time setting the sensor.

I started working on this. I called UI FC112 since the idea is based on FC11 and Anduril2. For now it’s mostly Anduril2 with stripped out functionalities. It’s based on source code of FSM, revision 583.

Differences from the UI chart:

- there is no separated moon mode in discrete modes

- 3C while off - batt check (4 blinks) -> beacon -> bike strobe

- 3C while on - ramp mode switch (like in Anduril)

- 2C while off - ramp ceiling

- 2H while off - momentary turbo

- 2C while on - turbo

  • 7C/7H left as are on Anduril2.

Following features were removed from Anduril2 (probably more but these I remember):

- configuration

- muggle/simple mode

  • party and candle strobes.

So LVP, thermal control should be working.

I flashed it to D4v2 10 minutes ago and it seems to be working :slight_smile:

Source code

HEX files (select the one you want, then click “Raw”, then save as hex file).

Feedback and comments are welcomed.

4 blinks is a bit coarse IMO. 5 is much better I think. I personally like the voltage readout, but wouldn’t have a problem with a 5 blink or color (roygb) readout if possible.

Having 2H work as momentary turbo while on OR off would be the only thing I’d recommend.

How many levels are in the stepped ramp?

To avoid GPL licensing issues you have to share source code.

Do you mean this?

(1) A weakness of Narsil/Andúril is the need to wait some time to be able to ramp up a second time after previously ramping up. This is unneccessary since we have 2H to ramp down. So, when on, 1H should always ramp up. Crescendo does better in this respect.

(2) I don’t see automatic memory in your diagram, but I presume it’s still there. Highly desireable feature.

Edit:

(3) Ramping speed should be made adjustable

If i understand correctly if you use someones open source code it have to stay open source .

I’ll try to change it.

But 2H while on is ramp down.

Currently it is Anduril2 default, usually 7.

I think you didn’t see a link to github in my first post, do you?

AFAIK it is like that.

In FC112, one click while off goes to last used level. Just like in Anduril and Anduril2.

It’s adjustable in firmware code. I guess the main point of this redesigned UI is simplicity, so there is no configuration in runtime.

Why in diagram 10C switches between ramping and discrete mode? What is wrong with 3C? Personally I switch between ramping and stepped modes pretty often.

“I think you didn’t see a link to github in my first post, do you?”
I did ,but you are not TP starter, do you?
I shared mine UIs based on FSM on FSM topic.

No, it ramps up or down depending on previous operation.

Yes, sorry, I meant manual memory.

The TP made only the diagram as a draft. There is no corresponding code for it.

Just checked it. In Anduril, Anduril2 and FC112 ramping direction is changed only if second click happened in ~1 second window. Otherwise it’s ramp up action.

Manual memory is not present on Lux-Perpetua’s diagram and also is not implemented in FC112.

:person_facepalming: twice I’ve now made this mistake.

Updates on FC112:

- added separate moon mode for discrete ramping :partying_face: - so the lowest mode is available from off, but later is not included in ramping, like in Lux-Perpetua’s chart

- updated manual: fc112-manual.md

  • reduced discrete ramping steps on most flashlight configurations

FC112 UI Manual

Source code

HEX files (select the one you want, then click “Raw”, then save as hex file).