Sure, why not? As long as you got a hex file to burn...
That’s awesome. Just to reassured that as I remembered TK did mentioned it is kinda no U turn. Thanks Tom E.
I'm speculating she may be referring to not doing anymore development on Anduril 1, so Anduril2 will get all future mods and support for new drivers and flashlights, etc.
That will be good to know. Thanks again.
[Edit: you can disregard this post; lockout 2H is the manual memory setting (if there is one) per the up to date manual]
Hi, I am still on anduril 2 compiled 2019-09-25 for D4v2, I thought I would still report before upgrading just in case it is indeed a bug and may have carried over:
When in lockout mode —> 2H, the second momentary brightness is stuck at around 10 or 20
I have now set the ceil of smooth, stepped and simple UI ramps to different higher levels (over 30). Didn’t change. Then I set smooth ramp ceil to 1.
However, lockout 2H is still stuck at around lvl 10, while 1H behaves as expected and is the lowest ceil of the ramps. I hope this helps.
Don’t know if it’ll help but per the anduril 2 manual
in the lockout section :
“2H: Light up at the highest floor level.
(or the manual mem level, if there is one)”
So your 2H is probably your manual mem setting…
Yup this is it thank you! Lockout 2H was my memory setting… This is probably why the Anduril2.hex was just published, that line of the manual wasn’t there on the 25th!
Anduril is great. Thank you Toykeeper and other helpers and contributors.
Take note that hybrid memory seems to affect the Lockout 2H as well, until the timer is up it will use the highest ceiling setting rather than your manual mem level. I was confused why this was happening until I let the light sit for a couple min.
D4Sv2 and KR4 are both using the 9/25 firmware and have been working perfectly so far. Haven’t done any graphing or real measurements other than a quick check with an IR thermometer, but thermal management seems to be functioning well- definitely stepping down when it needs to and smoothly as far as I can tell.
Lockout mode uses the manual memory level for 2H, if that level is non-zero. Otherwise it uses the higher of the two ramp floors. The hybrid memory timer is not even considered… and neither are the ceiling levels.
If your lockout 2H level changes after the light sits for a few minutes, something is broken.
The code is a pretty simple algorithm:
- If the user pressed 2H:
- By default, use the highest of the two ramp floors.
- If manual memory is enabled (at all), use that level instead.
That’s all. There is no logic to change brightness based on the amount of time it has been locked.
Indeed this is what I also experience: 2H is always the manual memory (unless manual memory is disabled) (on the older software compiled by myself the 25th).
Yeah, the “lowest floor first, highest floor or manual mem” thing was added on 2020-08-05. So it has been that way for a while. I just didn’t remember to update the documentation until a month and a half later.
Full details are in the revision history, for anyone who cares enough to look. There’s a lot of detail though, since there have been almost a hundred revisions in the anduril2 branch alone… in addition to the ~1160 or so revisions currently in the parent repository.
Just tried it again, must have hit the the first of the manual/hybrid mem menu options by mistake and disabled manual mem. When properly set 2H-lockout functioned as normal with hybrid mem enabled. 
Does anyone know the version that would work with the FT03 sst40? I was gonna red lash but it’s running narsil
Do you want Anduril 1 or 2 for the FT03? The driver requires some patches for the “uncommon” channel configuration. Here are the necessary changes:
If you like I can rebase it on the latest version of Anduril 2 tomorrow and send you a build.
@ToyKeeper
Would be great if you add a way to make this work upstream. For the 1634 the definitions are already in the hwdef config, maybe this should also be done for the 85.
Yeah that would be great, thank you so much
Just flashed my PL47G2 with anduril 2.When pressing 3C from off,I got this sequence:
-batt check
-beacon
-temp check
1)The sequence is different than explained in the manual(batt check,temp check,beacon, sos), is that normal?
2)Any idea why I don’t have sos mode?
SOS is probably disabled as a default. I always understood the order to be batt/beacon/temp - this is how Anduril and Anduril2 work, as far as I know. With Anduril2, you can disable beacon too (
)
Thanx, any idea how I can enable it?By editing the firmware file or by button presses?
I cannot find anything about it in the manual…
In config-default.h:
// boring strobes nobody really likes, but sometimes flashlight companies want
// (these replace the fun strobe group,
// so don't enable them at the same time as any of the above strobes)
//#define USE_POLICE_STROBE_MODE
//#define USE_SOS_MODE
//#define USE_SOS_MODE_IN_FF_GROUP // put SOS in the "boring strobes" mode
//#define USE_SOS_MODE_IN_BLINKY_GROUP // put SOS in the blinkies mode group
So, you have to edit this file, or add the #define's to your cfg file. It's compiled in or out, so you can't add it via the UI.