I’ve been working on developing my own version for personal use with the LT1S, and am stuck on changing 3H momentary turbo (for non-tint ramping channels) to instead blink 3x to indicate no tint ramping functionality on the current channel. Should be at ramp-mode.c, Lines 423ish and 446ish I believe. It’s the last thing I want changed, but can’t get it to work right…any suggestions?
Here’s my version:
// 3H: momentary turbo (on lights with no tint ramping)
// (or 4H when tint ramping is available)
else if ((event == EV_click3_hold)
#ifdef USE_CHANNEL_MODE_ARGS
|| (event == EV_click4_hold)
#endif
) {
// ramp tint if tint exists in this mode
if (event == EV_click3_hold){
if(channel_has_args(cfg.channel_mode)) {
return EVENT_NOT_HANDLED;
}
#if defined(USE_CHANNEL_MODE_ARGS) && !defined(USE_3H_CHANNEL_RAMP_TURBO_FALLTHROUGH)
//don't turbo on 3h
else {
if ((arg % 32 == 0)){
blip();
}
}
}
else {
#endif
if (! arg) { // first frame only, to allow thermal regulation to work
#ifdef USE_2C_STYLE_CONFIG
uint8_t tl = style_2c ? MAX_LEVEL : turbo_level;
set_level_and_therm_target(tl);
#else
set_level_and_therm_target(turbo_level);
#endif
}
return EVENT_HANDLED;
#if defined(USE_CHANNEL_MODE_ARGS) && !defined(USE_3H_CHANNEL_RAMP_TURBO_FALLTHROUGH)
}
#endif
}
You could replace if ((arg % 32 == 0)){ blip(); } (which will do it as long as held) with something like:
blip();
nice_delay_4ms(20);
blip();
nice_delay_4ms(20);
blip();
which should have the desired effect of only doing it 3x.
Edit: It might constantly restart though, in which case it might need to be:
if (!arg){
blip();
nice_delay_4ms(20);
blip();
nice_delay_4ms(20);
blip();
}
so it only starts the sequence on the first frame.
2 Thanks
Any luck fixing the pmw noise problem?
Comment - I am interested keep us posted on the status.
A few people on Reddit discussing the PWM noise too, which led me to remember I never pointed out the one I’m having - I can hear PWM above ~50% ramp and below 100% on red as well as both white channels (single or blended) but I don’t really hear it when blending white and red unless the ramp is high enough that it’s audible single-channel anyway.
I received my two LT1S lanterns today.
I haven’t tested them yet, but they look legit.
I still want to get another LT1S, so the next time they go on a crazy sale, I’ll snag another one. 
EDIT:
I tested the lanterns, and they work as expected.
Now I need to get some more 21700 cells (when they go on sale.)
I received the flashlight yesterday and so far I am quite satisfied with it.
Pros: small size but high power, nice warm white shade, good build quality.
Cons (as has already been mentioned): battery indicators too bright, auxiliary button LED invisible in low mode, PWM noise audible from 30 cm.
When I turn on the flashlight after a while, there is always the automatic Red/Warm/Cold auto tint mode, and when I switch to Warm/Cold ramping mode, the coloring is halfway between warm and cold.
Is there a way to memorize the warm/cold mode when turning on, and with the warm tint?
This is because 10 minute manual memory is initially enabled on this light, making it revert to what you’re describing after 10 minutes of being off. You have two options to change this with runtime configs, both of which you must first enter advanced UI mode to do (10H from off - it will blink once indicating this was a success):
Your first option, turn on the light, adjust it to your desired channel, tint, and brightness, and 10C to set that as the new default settings the light turns on with after 10 minutes of being off.
Otherwise, you can turn off this altogether and the light will always come on to whatever you last turned it off in → to do so, do 10H while the light is on to enter ramp config, then at the first blink, release and the light should begin flashing red, indicating you stopped on Item 1 of ramp config (manual memory deactivation) and it is now ready for your input. Click once and then wait, and manual memory should now be turned off. I haven’t done this on this lantern in runtime but I think this should be correct.
5 Thanks
Oh thanks! That was easy!
1 Thank
Having a weird issue with mine, and hoping it doesn’t mean my light is screwed up. Worked fine for about a week and now it’s staying in a very very low on mode — in red — when the light is turned off. I’ve tried resetting the light, and it’s still happening.
just successfully updated with Android ZflasherAVR using short and thick USB cable from Samsung external SSD - the photo was very helpful for finding the right direction - on the small pads there is no indication of R-+
My photo isnt the LT1S, but coincidentally it’s the same orientation.
It was super hard to read ± on the smaller pin set but if you follow the paths on the board to the other pinout it is much easier to read and then you can orient the flasher accordingly.
1 Thank
Yeah, same, I followed the traces, I didn’t even realise the small pads were labelled, maybe I just missed it.
Anyone has any issue with the onboard charging with the included battery?
Yesterday the included 21700 battery suddenly died. I only charged it with the built-in charging and the cycle time is probably just 3.
The light started to act weird and didn’t respond to many button actions. Popped another battery in and it is all good. Checked the battery with the Vapcell S4+ charger and it went from 3V to 4.2 in 5 seconds. Using discharge function, it went to 2.x V within 5 seconds again. Looks dead to me. If I installed that dead battery to other lights it also refused to work.
I have limited knowledge of the battery but per my understanding the light should never discharge the battery more than the safe low theshold. It is also my first time encountering a dead battery. My guess is it’s either the battery was already bad or the onboard charging caused this. However the light worked well previously with the battery (but not used very often).
Sofirn’s batteries have a higher failure rate than other brands, probably using cheaper cells from less-known manufacturers. Send them an email and you might get a replacement, make sure not to throw it away yet.
1 Thank
Thanks for the heads up. I already sent an email but as usual they requested some video to prove it. I am just worried that if it’s the onboard charger’s issue it will ruin my better 21700 now installed on the LT1S pro. Hopefully it’s just a bad cell.
For anyone who missed the group buy, LT1S Pro is now available on Aliexpress:
https://www.aliexpress.com/item/1005005674163460.html
"
1.The LT1S Pro uses Nichia LEDs, which provide a more natural and realistic lighting experience, making it perfect for outdoor activities such as camping and hiking.
"
Not explicitely mentioning 519a, but I don’t know what else it would be.
4 Thanks
That says neither Anduril nor what LED it is. I’d wait… it says there are 666 available.
Edit: the bottom section wasn’t initially showing up for me, but now it looks like it is the same as the first run. Hopefully it is. The LT1S Pro is really a great light and a lot easier to carry around than the LT1.
From the AE page. Doesn’t say 519a but does say Nichia.
Soven LT1S Pro is the latest upgraded version of LT1S. The LT1S Pro has several important upgrade features.
1.The LT1S Pro uses Nichia LEDs, which provide a more natural and realistic lighting experience, making it perfect for outdoor activities such as camping and hiking.
2.Anduril 2.0 user interface. Customize lighting and color temperature, adjust brightness levels to meet your needs