In the Hank Thread you helped me and compiled a version of the new Andúril 2 for the KR1 with SBt90.2 for me. (That was here)
Thanks again
I use the KR1 pretty much only in the new Tactical Mode. I like that most.
I realized though, that when not in tactical mode but in ramp mode, that the lamp then immediately ramps down brightness to approx level 2, after switching it on with brightness level 5, 6, 7 or Turbo. Even when the lamp is completely cold… the immediate ramping down is not temperature related
In tactical mode the lamp holds the brightness for a significantly longer amount of time.
When I go back to the previous Anduril version from 13/12/2021, then the lamp holds the ramp level 5 and 6 pretty constant and only ramps down level 7 and Turbo but after some time.
So as expected.
Could this be a bug in the new revision?
(I will try to do more research and tests tomorrow)
Sounds to me like your temperature calibration is off. Check your temperature when the light is room temperature, and if it’s wrong, 7H then enter the correct temperature.
Tactical mode doesn’t use thermal regulation, so it wouldn’t thermally step down like ramp mode does.
Thank you
I did check on the temp calibration and max temp settings yesterday but let me reinstall the 2023 firmware version later today and check again.
I understand this is the only setting that could affect the ramp down being too quick.
So must be it.
seee you later
I reinstalled the “anduril.2023-04-29.noctigon-kr4.hex” and calibrated temp settings to 21 degrees and set max temp to 55 degrees.
I then tested the behaviour after switching the light on at ramp level 5. And it directly decreases the brightness.
I made a video where I show the Opple readings (2.7m distance to Light) and how it decreases right after start on ramp 5.
At the end of the video I show the temperature reading by 3C → 2C, which results in 22 degrees.
After that I flashed the firmware back to “anduril.2021-12-13.noctigon-kr4.hex” to show how the brightness is kept and doesn’t ramp down right away. I also do the temp check there just for the sake of comparison and it’s 29 degrees, which makes sense since it heated up more…
I think the difference in magnitude of the Lux values is coming from different stepping in the 2 firmwares.
Sorry for the amateur videos.
But I hope this helps to describe the ramp down in the 2023 firmware that I mean.
Can anyone maybe reproduce this with a KR1 SBT90.2?
Edit: Edit: KR4 Dual Channel has the same ramp down issue. I could replicate this a couple of times.
D4K and D2 don’t have a ramp down issue with the corresponding firmware.
I tested the Post-Off voltage LED function with the Rev.710 version, with my model 0136 DM1.12. This function now works super. Together with the option to pre-set the duration of the voltage display, this all functions like a charm. Thanks for this update, a really nice improvement!
I find this hex choice situation a bit confusing. I also have a KR4 Dual Channel with W1 and 519A, but that is a model 0135, and was shipped from Hank (in December 2022) with the anduril.2021-12-13.emisar-d4sv2-tintramp.hex. This now runs on anduril.2023-04-25.emisar-2ch.hex, and that seems to work fine. Why do some of these run the D4SV2 tintramp firmware for model 0135, and others with the same specs seem to run on a kr4 hex? Is that different? What is the difference? Or do I misunderstand something here?
The multi-channel branch is awesome! I love the changes. Both on my dual channel (5700k dd +2700k dd) and single channel d4v2.
having 3 ”channels” accessible through 3C is a dream come true! 50-50 mix, cold, warm. Perfect.
Using the aux as a channel is an awesome feature. I wish it was an option for my dual channel light doesn’t have a proper moonlight level.
6c for brightness ramp style change (stepped or smooth) doesn’t bother me at all for now.
The tactical mode is very well implemented! I like how responsive it makes the switch too. Haven’t tried changing the brightness levels, but it’s pretty good. I might make the 2nd mode a bit brighter, or rather change the 3rd (strobe) to a medium brightnes.
The battery indicator at turn off is great. I believe it only works when aux are set to battery indicator, I would prefer if it were not tied to the aux setting, so it always showed battery level regardless of the color I set my aux at.
Also, when I hit make, it didn’t compile for the dm11 12v that my dw4 with boost driver uses. I hope it comes soon! This one really needs a moonlight channel!!
It would be cool if the tactical mode included adding aux colors to on of its modes
Thanks for these awesome new features! Anduril is reaching godmode level of user satisfaction!!
For the sake of avoidance of any doubt I redownloaded the anduril.2023-04-29.noctigon-kr4.hex again and reinstalled it → same ramp down behaviour.
Or is there a different place where more up to date versions can be downloaded?
In the end there was more development happening since the 29/04/2023, I think?
Hank has changed which firmware image is used for a model before, e.g. the DM1.12 originally had the K9.3 firmware, then changed to the D4S for newer versions. The kr4-tintramp firmware’s header file is just importing the d4sv2-tintramp-nofet config, then disabling the button LED, so that could be the difference. D4Sv2 with 519A or W2 on one channel get the DD FET enabled as well (0136), which is a D4S-only configuration. Overall, both the KR4 and D4S firmware probably get used in the most different lights overall, most dual channel lights use d4sv2-tintramp-nofet, the K9.3 and DM1.12 use d4sv2-tintramp-fet, and a lot of different single channel lights use the KR4 firmware.
Most Hanklights use the same pin layout on the MCU, which is why the emisar-2ch firmware works on most of them, but doesn’t use the DD FET for dual channel lights with it usable (D4S, DT8/K, DM1.12).
Is there a way I could compile a .hex for Hank’s 12V/6V boost drivers from the new multi-channel branch? It only compiles for a selection of models. (Edited typos)
I just can’t wait to add a red “aux channel” to these flashlights that don’t have a proper moonlight (dual channel lights could also benefit from an aux-channel).
There’s some migration that needs to be done to the new hwdef style, then it’s just adding and defining channel modes. Which build target are you looking for - KR4 (0216) or DM11 (0273)?
I apologize if I’ve missed this when I went looking…
While waiting patiently for the different iterations of the most recent A2 updates, I’ve been playing around with the 2023-04-29 versions of the D4SV2, Emisar 2-channel and KR4 hexes and the 2023-05-02 hex for the TS10. I am quite pleased with the updates across that board but I find myself with some things I’d like to either clarify or possibly suggest.
There seems to be a new function where when turning the Hank lights off, either from on or when using 1H & 2H in lockout, the Aux emitters give you a brief display of battery voltage - in the same way you can set the Aux emitters to provide a voltage readout with different colors meaning different battery levels…
BUT - this readout appears to ONLY use the Aux emitters on HIGH. My question here is whether or not I’ve missed something about this function while the Aux emitters are set to low. I set mine up so that when the light is unlocked, whatever color or mode I’ve chosen uses the Aux emitters on High, but when locked out they are on Low. I’ve noticed when I have the light locked out and use 1H for moonlight so I don’t wake the missus, the subsequent voltage readout will use the Aux on High before then returning to the Low setting I’d selected. Is this adjustable so the voltage check is ALSO on Low when I’ve set them normally to Low? If not, can the function be modified to work this way?
As for the TS10 firmware, I’ve found that the manual battery-check reads out the voltage using the Aux emitters, not the main emitters like in my other A2 lights… I find that I VERY much like this! Is this coming more broadly in future iterations?
The latest version (commit 710) has a threshold set where when the light was last used below that ramp level, it will use them on low instead, currently defaults to RAMP_SIZE/10, i.e. 15, so moon/floor will use low but most normal ramp usage will still use high.
If you set that to a higher level they would stay on low for higher levels the light was used at, or setting it to RAMP_SIZE would effectively always use low, or 0 always high.
If I’m understanding what you’re saying, it looks like this is the solution to my question! Connecting the Aux output to the last used output from the main emitters or the last used output from the Aux emitters… Either seems to offer the solution I am looking for. Very cool!
Thank you for the response - I appreciate you taking the time!
No problem, I enjoy hacking on it to learn, e.g. got the chance to learn some of how dynamic PWM works in FSM and a bit more about writing hwdefs doing this.
Built based on revision 710, aux channels added (main LEDs, red, yellow, green, cyan, blue, purple, white) and all defaulting to enabled, added a third item to the battery check 7H menu (2nd is seconds for voltage to display, 3rd is the ceiling for using low for the battery aux plus 1 (i.e. 0C = cancel without changing, 1C = set ceiling to 0, i.e. always use high, >=151C = ceiling to 151 i.e. always use low). 3C in battery check mode to cycle the channel use for blinkies.
2 different builds here: File folder on MEGA - anduril.noctigon-dm11-12v-aux.hex is as described above, and anduril.noctigon-dm11-12v-aux_4c_previous.hex has 4C mapped to go to the previous channel instead of lock from on. By default all 8 channels are enabled, if you don’t want some of them, use the 9H menu to choose which. Source included.
