I just noticed that the firmware for a set of Wurkkos lights is now published in @ToyKeeper’s repository. Currently right at the bottom here: Index of /torches/fsm/anduril2
Seems like @gchart and @ToyKeeper merged more than just the LTS1 Pro changes recently. Thank you to both for your work. Happy to have one fewer place to check for updates.
@ToyKeeper is working on specialized firmware configurations for Wurkkos flashlights AFAIK. So it’s more that just merging old configs.
Yeah, it’s really great to see the recent activity! I hope this is honored by Wurkkos and all other manufacturers using Anduril as well.
I’m updating every supported light, roughly in order of most convenient first, or most complicated first. I started with 3-channel like the LT1S Pro, and 2-channel like Hank’s tint-ramping lights, to make sure the multi-channel stuff would work… and I’ve also tossed in some 1-channel lights too.
The entire set is taking a while, but I’ll get it done eventually.
Thank you!
The accomplishments and contributions from “ToyKeeper”, "gchart"and others on this forum are truly amazing and appreciated.
30 years ago I programmed in C on UNIX systems. The C language has not changed much in that time, but I sure have and I cannot figure out how to isolate the source and configuration files for the various builds in the repository in order to compare them to determine what has changed and maybe begin to understand the code.
This post from forum member “thefreeman” provided a link to the configuration file for the Sofirn SP10 for revision 657 which helped me understand some of the default settings:
But I cannot figure out how to find the configuration files for other lights and revisions.
I would also like to be able to determine the functional differences between “anduril.2023-05-02.wurkkos-ts10.hex” and “anduril.2023-05-03.wurkkos-ts10.hex” (which are one day apart), but don’t even know where to begin looking in the repository or if a file exists that summarizes the difference or changes.
I have searched, but have not yet been able to locate a tutorial or guide that could help neophytes like myself understand the structure of the repository and its version control method so I could follow how the code has been changing and find the specific source and configuration files for various flashlights and revisions.
Any help on how or where to start (or links to helpful posts that I may have missed) for understanding the structure of the repository would be appreciated.
Thanks.
TBH, the repository is a mess which needs to be restructured, and the hosting platform is a mess too, so it needs to be moved to a better platform.
Regardless, here’s a rough process for finding the changes… First, here’s the base URL for the repository:
https://launchpad.net/flashlight-firmware
From there, click the “Code” tab at the top:
https://code.launchpad.net/flashlight-firmware
This shows a list of all the code branches, in order of most recent first (except for trunk, which is pinned to the top even if it’s old). The most recent one is the multi-channel branch, since I’ve been working on converting everything to a new method of handling multiple power channels and multiple sets of LEDs. It’s also the only one with a date within the range you were looking for:
https://code.launchpad.net/~toykeeper/flashlight-firmware/multi-channel
From there, scroll down a bit to see recent revisions. There have been a bunch though, so click the “All revisions” link at the bottom to see more.
https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/multi-channel/changes
… and this has full details on what changed.
The way it works now isn’t a good way to do it… it’s a lazy way to do things, and I should do better. I’ve just got a huge pile of things waiting to be done. Gotta finish the multi-channel branch, which involves sort of rewriting the code for all ~70 supported lights. Merge all the outstanding branches to simplify things for an upcoming migration. Export FSM to its own repository. Convert the repo to git, and put it on github. Update links and documentation to point to the new host. Rewrite the build configuration system to organize the files better, and make it easier to find and understand things. And hopefully make time to work on user-visible features too, and adding support for new lights.
Anyway, I hope this at least helps with finding what changed. And to get info about a particular light, look for its “cfg-.h" file. It should have details about how things are configured, and references to other files with additional details (like a "hwdef-.h” file).
There’s view branch changes and view revision when you can see the changes between revisions : ~toykeeper/flashlight-firmware/anduril2 : files for revision 657
Other cfg files are located here : ~toykeeper/flashlight-firmware/anduril2 : files for revision 657
Thanks to all for the helpful links.
The best part of my day is the time I spend on this forum.
Just wish I was younger with more lifetime remaining to get up to speed on the code and hardware.
Big thank you to all involved.
Have you checked out pijul yet? Seems right up your alley. Unfortunately, it’s probably a little too immature to commit (pun intended) to the nest, but I hope pijul picks up enough momentum to be a usable alternative to git.
I have looked into Pijul before. It has some interesting features. However, the reason for the move to git isn’t really about features or technical quality… the main appeal of git and github is that they are, by far, the most popular DVCS solution currently in use.
Git is what people are using, and the move is about the people, not the tool.
