And there is a similar configuration for locked out mode.
For off mode I use the battery indication mode, which I find quite useful. It displays blue aux LEDs as long as the battery is well charged, and after this displays green or even red.
Just for reference in case anyone else is wondering, I’m running a 60% FET max build on a FW3A with D220 219Bs without any issues and plan on running a 60% build on my D4v2 when I swap in a set of 219Bs. The 219 build variant posted in FSM is limited to 75% FET max iirc.
Forgive me if I missed this somewhere, but is this still an issue? I’ve noticed that my D4V2 Ti misses clicks sometimes. It’s kind of annoying when I try to unlock it, but instead change the aux mode. I love the light (and Anduril) otherwise, though!
I’ve noticed what may be considered a bug in Anduril. It occurs with my D4v2 and my FW1A. The issue is related to shortcutting to turbo from a ramping mode and then shortcutting back to ramping from turbo.
If the light is on at an arbitrary ramping level, a double click switches to turbo and then a second double click returns to ramping at the level it was last at. This seems to be the behavior regardless of the ramping level.
However, if I double click from off to shortcut to the highest ramping level, then double click a second time to turbo, and finally double click a third time to return to ramping, it sends me to the default ramp level (the single click from off level) rather than back to the highest ramp level from which I came.
Yes. Double click from off is a shortcut to temporary max ramp. The level is not remembered and next time you switch on the light it will return to the last used level (or to the manual memory level). When you return from turbo it will also return to this level.
I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.
Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.
The issue is that, at least in manual memory mode, the light always returns from turbo to the last ramping level it was at, unless that ramping level is max and the max ramp level was accessed via the shortcut from off. That, to me, is inconsistent and unexpected behavior.
If the light returns from turbo to max ramp if I accessed max ramp by ramping up, it should also return from turbo to max ramp if I accessed max ramp via the shortcut from off. There should not be two different flavors of the state “on and at max ramp”.
It is not only at max ramp. When you double click to turbo, then double click to return, Anduril will return to the remembered ramp level. That remembered level is not overwritten by any shortcut. So you will see the same behaviour if you reset the light (to cancel any previous remembered level) then click-hold to minimum ramp, then go to turbo and back. You will return to the default level after the reset, which is at the top regulated level in standard Anduril. That seems just fine.