I got mine partly for development purposes so I don’t mind which firmware it came with overall since I’ll be hacking on it anyway.
I’m fine waiting for updated firmware.
1 Thank
Interested.
I’ll wait for updated firmware. So I guess I can order soon.
Unfortunally my lantern got shipped already and I cant flash the new firmware because i dont have a flashing kit 
1 Thank
Mine has already been shipped, have Hanks flashing adapter,
so with correct pin assignment it should be ok, I think.
Thank for all your work and all your time!
Are you going to upload the hex files as well or do I need the complete build environment?
The hex files are available here already 
Hex files
Unfortunately that flashing adapter won’t work for this flashlight. You need a UPDI adapter like this one:
3 Thanks
will it be possible to order the LT1S Pro from Aliexpress?
My LT1S Pro turned up today, but it doesn’t turn turn on.
The only thing that works is the battery indicator on the top (2 bars for the included battery, 4 bars for a fully charged battery from a different torch).
Any suggestions?
My LT1S Pro seems to be DOA, blue led on the top comes on briefly, but lantern won’t turn on and it won’t charge. @Barry0892
Ugh, that’s not good. What’s the blue LED? My sample doesn’t have any blue LEDs that I’m aware of. Have you tried to do a factory reset?
The 4 blue battery indicator LEDs on the top of the device.
13 clicks does nothing unfortunately. Neither does holding power while tightening the battery tube.
The 4 blue LEDs on top indicate battery charge level. They run on a separate circuit, and they light up for 30 seconds after each button press. It shows that the battery is okay and the driver board is getting power.
The button LED is controlled by Anduril, so if it lights up, it suggests that the MCU is getting power and booting up. If the button LED doesn’t light up after connecting power, the MCU either isn’t getting power or doesn’t have working firmware or doesn’t have a usable connection to the button LED.
Two things to try, to get more info about what’s not working:
-
4C from Off: This should make the button LED blink every 2 seconds. If this doesn’t work, the MCU may be frozen or corrupted or something might not be soldered correctly.
-
1C from Off, then 4C: Assuming it has gchart’s firmware from September, this should make the button LED go very dim after the 1C, and then after 4C it should turn the red LEDs on.
If it fails the first test, the firmware is probably corrupt.
If it passes the first test but fails the second, that suggests the MCU is working but none of the main LEDs are getting power.
If it passes both tests (the red LEDs turn on), only the white LEDs aren’t getting power.
Charging (or not) is a different part of the circuit, which can fail without affecting the rest of the lantern.
1 Thank
Battery charge indicator leds were changed to blue from original lt1s amber?
1 Thank
All three of the ones that I have (LT1S) from the original run have blue leds.
Odd. My LT1S Pro sample has amber (or red or orange… something in that range).
When you say button LED are you referring to the 4 battery indicator LEDs? I don’t have a separate button that gets lit up.
Pressing the button once makes 2 out of 4 blue battery LEDs light up. They then go off after ~30sec
Neither of the 4C tests appear to do anything unfortunately.
Happy to see my order is not shipped, total noob here so I can’t flash. I prefer to wait updated firmware. Especially for thermal regulation Toykeeper just added. Thanks for your awesome job !