I already asked to optimize some of your code - it works ![]()
Patches are welcome. If it reduces rom size and doesnāt reduce functionality or maintainability, Iād call that a win.
The newer Wurkkos TS21 have flash pads
OK, thanks for the clarification.
Perfect, Wurkkos does it again (at least in terms of using the right MCU with the right flashing pads ;-)); on that note, how well does it powerbank functionality work? Any issues like the one I reported here?
Knowing what I know about ChatGPT, I would call that unlikely
ChatGPT IME has about the same level of āintelligenceā as your usual callcenter operator (no offense meant to either callcenter operators nor to ChatGPT), maybe it could reduce code size, but I would bet that it would come at the cost of legibility (and therefore maintenability).
Where is that code? Send it over already
As they say, the proof is in the pudding ā and so far we didnāt even smell it ![]()
Thanks for the clarification. I faintly remember that my FC13 blinked a different model right out of the box, but I reflashed it with your latest version right away so itās only a faint memory ![]()
Starting with simple UI disabled saves 2 bytes⦠![]()
/runs
Iām sure we could save a whole lot by getting rid of all the useless flashing and strobe modes right off the batt tooā¦
- runs and hides *

Iāve got compile-time options to remove those, and I hope to eventually make a build server where people can choose the options they want and get a custom .hex file on demand. So⦠while the comment may have been in jest, I actually do want to do something like that.
No running necessary IMO: for my own flashlights, I always compile with USE_SIMPLE_UI undefined, to take simple mode totally out of the picture (simple mode is for dummies, and I donāt want them laying their grubby hands on my lights anyway
)
It saves a few hundred bytes, and even better, it also saves me from 10Hāing every time I flash a light.
Only minus is, there is (was?) a bug in TKās code (at least on the multichannel branch) that generated a compile-time error if it was #undef ā I submitted a patch here and on her Launchpad repo but havenāt heard from her (yet?).
woohoo! Im in. YOLO. I will take itā¦
![]()
Thank you! ![]()
I did see it⦠Iāve just had very limited time I can spend on it because of health issues which arenāt resolved yet. So Iām constantly trying to catch up on a ton of things.
We all appreciate your work, always take care of yourself when you need to.
(something something githubā¦)
Let me know, Iād definitely be willing to collaborate on something like that, I have the very beginnings of one but Iām also not someone who at all enjoys building GUIs or WebUIs so it will probably end up being a command line script or something otherwise.
Hi!
Could you PM me once itās back in stock?
Cheers.
I will.
Hey TK, no prob and no hurry. I didnāt mean it to sound like a complaint or anything, on the contrary: we are all just extremely grateful for your great work on Anduril and your insightful comments and tips here in BLF and everywhere else.
Sorry to hear about your health issues
Please take care of yourself first, all the rest can and will wait. I hope you recover fully and promptly, long life and prosperity to our Anduril queen! ![]()
Ditto, and ditto. Iāve also started sketching one, but if it ever comes to fruition (not a lot of time these days) it would certainly have no GUI nor WebUI, at maximum a BUI (Butt-Ugly Interface
), just like my own āweb siteā. 1990s plain-and-simple HTML rules ![]()
@thefreeman Iāll hold off on selling any more V2 adapters.
One adapter made a popping noise and had a burning smell after being connected to a PCās USB-A port for 3-5 minutes. Root cause unknown. Theyāre kindly sending it back to me to take a look.
I had three orders. Iāve notified each person and issued a refund.
Itās likely an isolated event, I wouldnāt worry about it. These chips arenāt exactly high quality, I had a few that were dead and weeded out during my testing. Just refund/replace the faulty one like you did.
BTW I should mention that since the start of the year Iāve been shipping a 3.3V version, the first version was 5V like Gchartās. The reason is broader driver component compatibility i.e. components with maximum voltage lower than 5V, for example I used a 4.6V max component in a driver I designed for a client.