I've been doing further testing (and minor modding) Anduril2 on the TK-35 light.
If I enabled START_AT_MEMORIZED_LEVEL, I ran out of code space again, so undef'ed USE_SUNSET_TIMER and that brought it down once again.
I also added a USE_2C_MAX_TURBO setting. What this setting does is always have the 2C go to max turbo, not max ceiling. But for Simple UI, works as it did before.
Modded code snippet in ramp-mode.c below.
TK: Not sure if you want to use it, but if you do, you have my permission:
// 2 clicks: go to/from highest level
else if (event == EV_2clicks) {
// simple UI: to/from ceiling
// full UI: to/from ceiling if mem < ceiling,
// or to/from turbo if mem >= ceiling
uint8_t turbo_level;
// TE 2020-09-18: Add compile switch for Making 2C the max
#ifdef USE_2C_MAX_TURBO
turbo_level = MAX_LEVEL;
#ifdef USE_SIMPLE_UI
if (simple_ui_active)
turbo_level = mode_max;
#endif
#else
if ((memorized_level < mode_max)
#ifdef USE_SIMPLE_UI
|| simple_ui_active
#endif
) { turbo_level = mode_max; }
else { turbo_level = MAX_LEVEL; }
#endif
if (actual_level < turbo_level) {
// true turbo, not the mode-specific ceiling
set_level_and_therm_target(turbo_level);
}
else {
set_level_and_therm_target(memorized_level);
}
#ifdef USE_SUNSET_TIMER
timer_orig_level = actual_level;
#endif
return MISCHIEF_MANAGED;
}</code></pre>
I have not tested it yet - will do so tomorrow.
This is the section of the cfg file I've added:
//---------------------------------------------------------------------------------------------
// TE - changes:
//---------------------------------------------------------------------------------------------
#undef DEFAULT_THERM_CEIL
#define DEFAULT_THERM_CEIL 60 // from 45 -> 60
#define MAX_THERM_CEIL 90 // from 70 -> 90
#define USE_2C_MAX_TURBO
// TE 2020-09-18" Take away Beacon and Sunset Timer to get the code down under 8 KB!!
#undef USE_BEACON_MODE
#undef USE_SUNSET_TIMER
// For the TK-35, enable this!
#define START_AT_MEMORIZED_LEVEL
If you can find the right place to put it, the -fwhole-program flag might help. That tells it to skip all the steps which enable linking multiple object files together, and instead assume the program consists of only one .c file. I’ve written FSM and Anduril in a weird way which makes that possible, and it saves a few hundred bytes on top of the other optimization settings.
This should get the Emisar D4 (v1) build down to about 7758 bytes in the default configuration. For blf-q8, I’m getting 8110 bytes.
Or maybe it’s due to some of the other flags. Here’s my build process:
But yeah, it’s definitely getting closer and closer to the point where no more can be added without overflowing. On some build targets, I’ve already had to start removing things. (mostly just MF01-Mini and ROT66)
I’m considering a major change to how the menu system works, to reduce code size and to change the interface style. Instead of waiting through each option to time out before moving on to the next, it would let the user skip directly to the desired option. Basically, just hold the button until it blinks N times, to access option number N, then let go to trigger the numeric entry prompt. The downside, is that it would only allow changing one option per invocation… and would require people to re-learn part of the UI.
Yes, in simple mode it’s meant to blink out once and then exit. People don’t like getting stuck in “disco modes” (*), so it makes sure exit on its own.
However, I’m not incredibly happy with how battcheck and version check work in one-time mode (where they blink out once and then exit). There’s a bug which can sometimes eat the next button press afterward, and it’s a very difficult bug to fix since it’s deep in the state-change mechanisms. Basically, state changes are instantaneous… but they need to be put in a queue for later handling. This timing discrepancy can cause some problems depending on how the program is written, and the fix is rather a pain to implement and would increase the program size significantly. So for now, it just eats a button press sometimes after version check ends.
Anyway, about the version numbers, it recently changed to a new format:
YYYYMMDDBBPP
YYYYMMDD: Year/month/day the program was compiled, or whatever version.h has in it.
BBPP: 4-digit brand / product model code, specified in cfg-*.h. A list of brands is in the MODELS file.
The model number serves a couple purposes. For one, it lets people know exactly which build and which configuration their light uses… even if the firmware was copied from another light. This has been happening a lot lately. It also makes it easy to detect when a company reuses code from another light, vs when they create new firmware customized for that specific model. Like, it’ll be easy to tell when Astrolux uses code built for an Emisar product, for example. Or when a D1 ships with a D4v2 tiny1634 driver instead of the older D1 tiny85 driver.
The make models command produces a list of all known model numbers. At the moment, this is what it says:
* As of a few days ago, there is actually a mode called “disco” mode. It flashes the RGB aux LEDs in random patterns at a high speed, and is an option for use during Off mode or Lockout mode.
Thanks, I added that as a compile-time option. By default it’s turned off, but can be enabled per build target or in config-default.h to affect all build targets.
Turning it on saves 4 bytes and reverts “Ramp 2C” back to how it behaved in Anduril 1.
There is also an “Off 2H” action to access momentary turbo (or momentary ceiling in simple mode). This has changed from the old behavior of “Off 2H” being a shortcut to “ceiling, then ramp down if held”.
I really like the candle-mode, but most times it is too “nervous”- the flickering rate is high for me. Is ist possible to implement an adjustable “framerate”? So brightness & flickering could be matched to the situation. I would love the possibility : ) The lightning mode could also benefit from this (okay, in this case only the pauses should be shortened/extended).
Will it be possible to update old drivers? I can’t relly get, what “it would break backward compatibility” means.
The intensity of candle mode can be configured at compile time by setting CANDLE_AMPLITUDE to a different value. The default is 25. It controls the difference between the dimmest and brightest parts of the animation. With lower values, it makes the individual steps easier to see, so it looks less smooth. With higher values, it’s more smooth but flickers too intensely like it’s a camp fire instead of a candle.
At some point, I’m hoping to increase the frame rate and/or make it use intermediate steps between the ~25 ramp levels it uses, to make it look more smooth without increasing the intensity. However, this is … tricky.
Old drivers can be updated, but it depends on the type of light. Some are easy, some require soldering to access the right parts, and some are glued so thoroughly they’re nearly impossible to open.
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:
UI config to drop thermal regulation altogether
For Off 3X clicks: BattCheck -> TempCheck -> Version# (like the old Narsil). Still think this would go well together in Anduril.
UI config or compile switch for 2C from OFF to set max turbo instead of top of ramp
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
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:
Go to the code. Any part of the repository should be fine.
Click “view revision”.
Click “download tarball”.
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…
Install Debian or Ubuntu somehow (like inside of WSL, Windows Subsystem for Linux).
Get root access with “sudo bash” or “su”, so you can install packages.
apt install build-essential gcc-avr avr-libc binutils-avr avrdude brz make
(okay, in this case only the pauses should be shortened/extended).
