Can’t believe sofirn didn’t use a better location, or at least make it easier to access. Wonder if the diffuser and tube can unscrew, to have better driver access.
Also, are those 2 sets of flashling pads? Hopefully the small ones are compatible with the TS10 flashing adapter.
I’m not sure how to disassemble it. If it unscrews, it doesn’t unscrew easily.
There are indeed 2 sets of flashing pads… which I thought was odd at first, but it ended up being really handy in this situation. The small one looks like it’s probably the right size for gchart’s adapter, though I couldn’t fit it in to confirm… and the larger set is just the right size for the ribbon cables I happened to have on hand.
That meant the only tricky part was figuring out how to get pogo pins onto a long enough stick to reach inside. And as luck would have it, I found a plastic fork which was exactly the right size and shape!
Doesn’t look too difficult to disassemble enough so that the 2700k 519a can be dedomed. Shame that the battery tube is fixed in place, or not removable otherwise.
What’s this device? Is it some kind of multipurpose programmer that can do the job of the gchart flashing key, the hanklight flashing thingy and also flash to different pad layouts?
If it is what I think it is, then can it be used with the ZFlasher app on Android?
It’s the flashing adapter gchart sent me a long time ago for t1616. It’s a jtag dongle which I think he may have replaced the firmware on, to do jtag2updi instead. The t1616 speaks UPDI… which always makes me think of UPDOG.
Gchart’s newer flashing key is smaller and generally nicer, but it’s all-in-one so it doesn’t have a way to connect a ribbon cable. I had to get the old one out for ribbon cable purposes.
I have no idea if it works with ZFlasher. I’ve never tried to flash firmware from a phone.
I’m interested in the group buy, but bugs are a concern since it will be the first batch of lt1s pros. Not sure if it’s better to wait for the finalised version.
FWIW, I’ve been rewriting the entire tint and channel handling part of the code, and have 2 of the channel modes working on LT1S Pro now. So in my dev version, it has:
white blend mode (adjustable CCT)
red-only mode
I’m also adding:
3-channel auto-tint mode (auto red → warm → cool based on brightness, like fire)
white + red blend
… and some extras or improvements:
ability to enable or disable each channel mode, so you can take unused ones out of the rotation
dynamic PWM for lower lows and a smoother ramp (I hope)
reduced power on moon mode (I hope)
red+white strobe mode
This new channel system requires updating every supported light though, so it’s going a bit slow. It’s the biggest code change since rewriting Anduril 1 to make Anduril 2.
You’re amazing, thank you for all your work! I don’t have any Anduril lights yet (this will be my first once it’s released), so forgive me if this is already a feature now, but would it be easy to also add the ability to configure the flicker speed on candle mode? I was reading many wish for a calmer candle flicker on the original BLF LT1, and I saw starryally’s Anduril 2 fork has this but not for the LT1 series of course.
I don’t have any runtime config options for that yet. Without recompiling, it just has brightness and color mode. Changing the speed or intensity still requires source code modifications.
However, I just added a 2-color police strobe which flashes red a few times then flashes white a few times, and repeats. Because that’s exactly what everyone wants in their camping lanterns, right?
(really, it was an obvious test to try using the new channel code at a UI level … but also, people have asked for something like that several times over the years)
As for a calmer candle mode… putting it in red mode makes it a lot less intense. Not because of the color, but because it uses a QX7138 chip for that channel… and that chip has some strange behavior. It doesn’t strictly behave according to the PWM signal it is given… instead, it takes its control signal as more of a suggestion. The MCU can tell it to go to exactly brightness level 58 of 255, and it’ll at least go in that general direction… but it stops whenever it feels like it’s close enough, and kinda makes its own decisions about if and when to move when the control signal changes. So sometimes instead of flickering like a candle, it’ll just stop and wait for a while. This quirk is also visible sometimes in bike mode and factory reset mode.
Good news, everyone! The group-buy for the LT1S Pro is officially on! This is your chance to get this lantern for $49.99, which is $20 off the regular price! The Group-buy discount code: LT1SPROBLF The stocks are limited and once they are gone, they are gone. Click here to secure your LT1S Pro now and enjoy the benefits of this versatile and reliable lantern!
The BLF new version has a safety feature that prevents me from sending the same group-buy message to multiple people. This is to avoid spamming and abuse. I have messaged some of you individually. I have also posted the group-buy discount code here. Please let me know if you have any questions or concerns.
I’ve got the 4 channel modes implemented, but am still working on adding thermal regulation, dynamic PWM, lower lows, and the channel config menu.
… and updating all the other lights in the repository to use the new system, including new channel modes on several other lights.
The way it works is:
3C: next channel mode
3H: adjust the parameter (if any) for the current channel mode
These work globally, anywhere which doesn’t have those actions defined. To make it work in ramp mode, I moved the smooth/stepped ramp toggle to 6C (but it still works via 3C when only one channel mode is enabled).
The 4 LT1S Pro channel modes are:
white blend (warm to cool adjustable)
auto tint (red when dim, warm at med levels, cool when high)
red only
wolfgirl42’s white + red mode (add an adjustable amount of red to the white blend, to lower the CCT and make red colors “pop”)
Default for now is mode 2, auto tint. But it’s easy to change (3C while on), and the user can enable or disable each mode, to get unused modes out of the rotation.
I haven’t sent out any code yet, since a lot of internals are still in flux, but once that stabilizes a bit I’ll get the code published.