Anduril ... 2?

At the moment, if a default blink channel is not defined, the entire feature to change blinky mode channel is not included at compile-time. Some older builds did not set a default for some lights, although I think now all the currently functioning ones have been updated.

1 Thank

That is precisely why I’m reluctant to use aux by default. It’s pretty common to use firmware on hardware it wasn’t written for, so I like to err on the safe side with features like this. I’ve been gradually converting builds back to the main LEDs for number blinks, but keeping the option to let the user change the channel if desired.

KR4 519 (ex SW45) added anduril.2023-05-30.noctigon-kr4-nofet.hex
What are the new function?
Aux Police mode in Strobe mode can be modified?
I was hoping to find Aux LEDs for battery check and now I am blind :rofl:

I’ve been using these instructions and they work great. However, what is the proper way to update my local anduril files with the latest in the repo? Do i just run the brz command again?

Hi Wolfgirl

I am sorry to only be a bad messenger here, but I can reproduce still a ramp down issue with this latest firmware anduril.noctigon-kr4.hex.

After a fresh install, when I set the temperature of my KR1 SBT90.2 or KR1 SFN60 in 3C–>2C–>7H -blink- 21C, then the immediate ramp down comes back.

Also after a firmware reset (13H).

The anduril.2023-05-30.noctigon-kr4.hex firmware from Toykeeper doesn’t seem to have that issue.

Edit: Same for the KR4 Dual Channel Firmware, but here also the Version anduril.2023-05-5.noctigon-kr4-2ch.hex from @ToyKeeper goes into ramp down after factory reset.

Well, I didn’t fix (or even find…) the bug myself, these builds are really just for convenience so people who want to participate in testing/development can without having to figure out the build toolchain themselves or ask TK for builds for specific lights, so you’ll have to wait for her response, but good to know I guess.

Hi Wolfgirl
I just thought that the newer builds would include the latest changes/fixes from Toykeeper and therefore thought it was worth mentioning.
I still didn’t get the the brz command to work on my Macbook, so I can’t do build myself yet and I haven’t seen how the process goes.
The builds you provide are very much appreciated and I hope my message above didn’t come acress the wrong way :slight_smile:

No problem, no offence taken :wink:

1 Thank

Yes!
I managed to get breezy to work on my Mac and basically I can now create hex files after doing:

brz branch lp:~toykeeper/flashlight-firmware/anduril2
cd anduril2/ToyKeeper/spaghetti-monster/anduril
make

But I think I understand one thing now.
The very latest firmwares aren’t yet in that launchpad repository, right?

So I couldn’t create the same hex files as Toykeeper at the moment.

(No problem with that, I don’t want to appear to be in a rush, just trying to understand)

:innocent:

The recent changes are in the multi-channel branch, not anduril2.

2 Thanks

Thanks, I found it.

Edit: Thanks again - this works great :smiley:

This is great fun - maybe someone else here remembers how cool it is to define their own personal default setting Anduril for the first time :slight_smile:

I am stuck with an item and haven’t found a documentation for that yet.

Tactical Mode:
I would like to have the tactical mode set in brightness 50, 100, 150

I change the “tactical-mode.h” to the below code, but it the hex-file still gives the lamp the original “TACTICAL_LEVELS 50,100,(RAMP_SIZE+3)”.

Is there a documentation that explains this code a bit better or could someone have an idea, how to make the 50, 100, 150 happen?

Thanks a lot in advance for all the support :slight_smile:

#ifndef TACTICAL_LEVELS
#define TACTICAL_LEVELS 50,100,150
#endif

// tactical(ish) mode
uint8_t tactical_state(Event event, uint16_t arg);
uint8_t tactical_config_state(Event event, uint16_t arg);

Edit the config header file for your light (i.e. cfg-${model}.h, e.g. cfg-emisar-d4sv2.h). The ifndef block only sets a default if TACTICAL_LEVELS hasn’t already been defined, and it should have been defined in the light’s headerfile.

3 Thanks

Thanks Wolfgirl!

Next task for me: default settings for RGB lights :slight_smile:

The latest SC31Pro have anduril 2.

What would be the equivalent?

Since SC31Pro is not listed.

Or do I have to look at the version and look for the one the manufacturer uses?

I don’t mind compiling it but I don’t know which one it was based on I don’t know the micro it carries.

Thanks.

The only reliable way to get the correct .hex file or build target is to use the version check function and MODELS file, as described here:

http://toykeeper.net/torches/fsm/anduril2/README
http://toykeeper.net/torches/fsm/anduril2/MODELS

Ok thanks!

Last time from several flashes the last 3 I counted 764 and it doesn’t exist.

I will count it again.

I’m confused by the comma or space and long space a 0?

I leave videos looks like the year 2022 because there is no such version or 022.

I leave a video from two perspectives if you see it well.

Thank you!

SC31Pro versiĂłn Horizontal

SC31Pro VersiĂłn vertical

Edit:
Maybe this one?

2022-2-8-614

0614 sofirn-sp36-t1616

Yes, that’s correct… I’ld write it this way:
202202080614 but that doesn’t change anything.

Perfect!!!

I get confused between long spaces and short spaces and very short spaces.

Edit:

I have an older 2022 version if there are 2023 versions!

Thanks.