【convoy】H4 and B35AM options are updated

SBT90.2 LED is not as common as CREE XML2, LUMINUS SST20 . There is basically no chance to choose BIN. I can only buy whatever BIN the supplier has.

:smiley: AliExpress often shuts down the mailing channels in some countries without notice.
I added Belgium to the seller’s shipping method, and I will use epacket to ship the goods to Belgium.

Would this firmware work on the Reverse clicky S21A S12 C8, and S2, L21A, M21A ?

Great, simplifying idea indeed.

2700K is a great CCT, it's :-) tungsten. Very adequate for nighttime illumination without causing any discomfort.

Pretty sure it can be obtained. Are you speaking of the LH351D? Simon has SST-20's in that CCT, doesn't it?

I sort of wonder why is it so common for “cool” CCTs to be used in the (flashlight) led industry, it just does not make sense unless you presume or recognize that the buyer is a dimwit, an ignorant in lighting disciplines.

no ,not suitable ,
But I have a program similar to crescendo, and the manufacturer is writing the code for me.

thank you for your sharing

Because most people think that light with cool color temperatures is brighter, they only pursue high brightness, not eye comfort.

Agreed - the same emitter in different CCTs will look brighter at cooler temperatures. Also yep, LH351D 2700K is definitely available.

@oweban

@Blggg

I communicated with the driver manufacturer and there is no problem with the code. In order to avoid difficulty in entering the mode selection, the response time for 10 clicks of the button is not very short. The user is constantly clicking the button, and originally just want to switch the mode, it may accidentally enter the mode selection. When clicking the 11th time, it will automatically Back to group 1.
There are two ways to solve this problem. The first is to shorten the response time, and the second is to increase the number of button clicks. At present, I don’t want to use the first method, because some users’ finger flexibility is not so high. I want to increase the number of clicks to 15,

Increase to 20. It’s a safe minimum. In normal use, mode groups doesn’t change all the time anyway.

That’s great news. Such program for S21A S12 C8, and S2, L21A, M21A will be enormous value.

I personally feel that 20 times is too much, :face_with_monocle:

I’m not only one that think 20 is ok. It’s a safe solution, and entering the settings, even for someone unfamiliar with flashlights, takes 3 seconds, maybe less.

There are 8 modes in the first group. It is enough to do two cycles to enter the settings. For example, when you start from the first mode and want to check the battery level and accidentally jump back to the first mode because you did it too quickly. And again you make 7 clicks, but then instead of checking the battery status you enter the settings.

This is an extreme example, but it shows what’s going on.

And as I mentioned before. In normal use, you don’t change the group every hour to make it annoying.

It’s not.

Change mode groups is not something one does daily.

Acessing the programing mode while being used by a person who doesn’t know there is such a thing can be dangerous.

And this is why I like drivers that have hardware so you can edit firmware. On the attiny13 drivers I could rewrite my own firmware to change that….

I do like constant current and far less heat, though.

Here is the problem: the response time or click/tap delay time for config mode is too long. This is obvious. I can tap a flashlight button 4 times per second without difficulty, and I am pretty sure any minimally trained or blessed human being can do it a minimum of 3 times per second.

As a first solution, click/tap delay time for config mode should not be set any slower than for any other click/tap sequence. This alone can be enough to fix the whole problem. However, if an increase in the lenght of the sequence of clicks/taps is considered, why does the number of clicks or taps needs to be a rounded figure or sort of? It doesn't needs to. Just increase it slightly. Set it at 12, 13, 16, whatever! This is no ramdom stuff! All is precisely pre-defined and once the user knows how to and is dexterous carrying out a procedure, he will just do it.

Do you know about when LH351D 4000K will be available?

I agree, I feel like the config mode should be simple enough for anyone to use. Whether they have fast fingers of a piano player or their fingers are slow and half frozen. Not everyone can click with a rythm and timing.

Is the config menu absolutely necessary?

Maybe we could make a lot of people happy with a simple step ramping or smooth ramping.

1 Click to Turn flashlight off, Click to turn on
2 To turn ‘memory on’ , just simple full click+hold. Ramp up and down to a level you want.Then let go to memorize the level.

3 To turn memory off using tailcap just Click and Hold +Unscrew and screw back tail cap while holding the switch.

Would this solve any issues people accidentally getting into config ?

It’s a mechanical switch, a UI like that is not possible. Any “hold” action will turn the light off during it’s duration.