Usually a “bzr pull” or “brz pull” should do the trick… if you downloaded it with a “bzr branch” originally and haven’t modified any of the files it tracks.
If modified, then you’d have to commit your changes and then “bzr merge” to get the things which changed. And if you changed the same parts I did, it’ll have merge conflicts. So usually I keep one copy to mirror what’s upstream, and another copy that I can work in.
Hhmm, don't know the bazaar commands, after all, they are bazaar 
I just dnld. All I'm doing at this point is creating and modding cfg files. Also modded anduril.c to load the cfg file I want to use.
Been using git at work and recently just recently did branch and merges, but we use tortoise git as the git UI.
I'm not seeing much right now that I want to change - you've been adding most things I wanted, like voltage calibration.
I created a running list of possible future mods and this is what it looks like now:
Beacon mode can be dropped now, and that I had as a custom mod before.
A bigger change would be to support 2 e-switches but that might have to be done as a different SM UI, think as you mentioned before. I got a couple 2 e-switch lights to mod but would need the driver support as well, though could wire up a modded driver.
Some feedback another photographer, is that they didn’t realize that stepped ramping was available. Maybe the diagram needs to show two separate parallel bars, one for ramping and the other for stepped ramping, with the 3 click link?
If my two cents are helpful, changing one option per invocation fits my personal workflow better. I usually need to figure out and think carefully about my intended setting and how many clicks it needs, such that I’m not thinking about the next setting anyway and will need to go back. E.g., calibrating the flashlight temp to room temp requires me to get the room temp, convert to C and get the # of clicks, letting the flashlight rest, quickly getting into temp config, and then rattling away the clicks. I’m in no mental state to quickly jump into what I want the temperature ceiling to be, or how many clicks above 30C that is.
Yeah, out of all the changes in Anduril 2, reworking the diagram has ended up taking the longest. It’s tricky to arrange so much info in visual form and still keep the layout clean.
I’m not surprised the documentation is taking time.
Along with things like simple mode, documentation is a huge part of having an accessible UI. If the docs are good then manufacturers will be happier that their lights are targeting all users instead of just experts. It also makes it easier for us to lend or recommend lights with Anduril to others.
The state diagram is great and my brain grocks it. I wonder if a more task-oriented diagram (similar to the text manual doc) would be more helpful to others.
I’m imagining this taking the form of a more tutorial style set of images or maybe even GIFs and a bit of HTML holding them together.
As with the text manual, this would allow someone to have a useful flashlight even if they didn’t get to the end.
This would take even more work than the existing docs though.
I don’t think Launchpad allows previewing HTML but if it did then that’d be perfect.
Have you considered a website or even a domain that redirects to the readme?
(Opinions from a random internet stranger. Feel free to ignore)
I got 3 lights running Anduril2. About to dnld to a HK04. I did some light rev engineering on the HK04. They use a 3 leg part (FET?) with resistors preceding it to implement the single 7135 channel. Turns out they precisely reproduced 0.35 amps with the circuitry! I tested it simply by lots of measured ramping over the first flicker - seems pretty dead on averaged to 0.35 amps.
The HK04 driver uses 2 large/typical FET's in parallel for the main FET channel, and has switch LED's, and USB-C charging. The charging appears to share the one color switch LED, and uses another switch LED - I think they are green and red. I destroyed the switch PCB in getting it out so am replacing it, but don't have a 2 color (4 wire) switch PCB to use, so not supporting the 2nd color for charging. The one I'm suing though has 4 LED's but all wired together.
So even though it's a custom ATTiny85 based driver, it looks like a FET+1 with 1 color AUX/switch LED's to the firmware. Interesting...
I’m sorry if this has been covered already, but there is no downloadable hex file for Anduril 2 yet, correct? The firmware repository website layout has me on the verge of a stroke (there doesn’t seem to be a file associated with each “revision”?) and want to make sure I didn’t miss something 
Correct, at the moment you have to compile it yourself.
The docs are taking a while mostly because I’ve hardly had any time to work on it. I have a lot of a tutorial written up, and mostly just need to make the diagrams to go along with it. The plan is to start with the simplest parts, then proceed in order of increasing complexity. People wouldn’t need to read the whole thing to use a light; just the beginning.
About short URLs, there is one which links to the latest revision in the repository, but I don’t have one specifically for the manual. I’m planning to put the tutorial up here on BLF as its own thread.
That seems to be a common issue. People don’t have bzr (or brz), which are the intended ways to access the repository… so they look for a way to download the whole thing, and can’t find it. It’s a pretty legit problem with Launchpad. However, there is a way to do it:
Then extract the .tgz file.
However, if you’re going to be compiling it anyway, it’s probably easier to just use a Linux container. Compiling it can be a little tricky otherwise. So for that, the process would be a bit different…
apt install build-essential gcc-avr avr-libc binutils-avr avrdude brz makebrz branch lp:~toykeeper/flashlight-firmware/anduril2cd anduril2/ToyKeeper/spaghetti-monster/andurilmakeOr something like that, anyway. Has been a long time since I set up a new host for this.
This should produce a full set of supported builds… one .hex file for each cfg-*.h file.
I’m not sure if avrdude actually works from inside of WSL. It may be necessary to flash using a Windows tool instead.
Thank you Sammy and TK! I’ve got some free time the next few days so maybe this is something I’ll mess around with. 
I'm compiling Anduril2 fine under Windows using AS 7.0, all source files combined in one folder
I haven’t compiled Anduril2 (yet), but that’s how I always compile the original.
:BEER:
One last question, I’ve downloaded the .tgz which seems to contain the entire repository but I’m still not sure what the actual file path and names are for Anduril 2. It just seems to be the latest revision (I assume?) of Anduril and the different model-specific files - is it just the ones under spaghetti-monster>anduril?
Yep - you trace it down under TK, under Spaghetti Monster, then Anduril -- that Anduril is Anduril 2 - check the manual, think there's another way too. Not on my home computer right now...
I am still changing Anduril.c to include the cfg file of choice.. I've made up 1 or 2 cfg files as well.
The hardware definitions are in ToyKeeper, fsm in ToyKeeper/spaghetti-monster and anduril (2) itself in ToyKeeper/spaghetti-monster/anduril. So these are the required files:
ToyKeeper/
├── hwdef-*
├── spaghetti-monster
│ ├── anduril
│ │ └── *
│ ├── fsm-*
│ ├── spaghetti-monster.h
└── tk-*
Yea, that looks correct. I simply re-used the solution and project files I had used on the old Anduril and it compiles/links. But if you want a complete proper project file for searching, etc., then you need to add all the new *.c files that Anduril.c includes, but specify to not compile them, just include them in the project -- this is what I did but not sure if I'm 100% accurate with it.
Awesome input everyone, thanks again!
If I had just “RTFM” I would have quickly realized it was v2 since it explains Simple UI, etc.
Edit: Getting two errors when trying to build (big surprise! - I’m in way over my head here haha)
First is “config-default.h: no such file or directory”
Then “recipe for target ‘main.o’ failed”
First thing I noticed was that in the atmel tutorial here the OP mentions that pasting in the Anduril.c code should rename main.c to that… that never occurred for me.
I did a quick search and there was some mention of user/file path names having spaces or weird characters causing issues. Even starting and saving with the project at the top directory of my D: drive didn’t eliminate either error though.
Second error has a log file but it seems there isn’t a compact code posting option on this forum and I don’t want to spam the whole page.
Using Atmel on W10 BTW
Yeah, that’s why I suggest using a Linux container, so you can use the project’s build system instead of rolling your own. The build is getting increasingly complicated with the way the files are organized, the compiler flags required to get everything to fit, and the multiple build targets. Building outside the included system requires finding solutions for all those things.
Updating to new versions is also much easier in a Linux container, since it only requires a “bzr pull” to grab the latest changes, or “bzr merge ; bzr commit” in the case that you’ve made your own local changes and want to integrate upstream changes too.