Emisar D4v2 (EA21 LED): party strobe mode doesn't seem to work correctly

Just got a new Emisar D4v2 with Nichia EA21 LED.

Doing a version check, it appears to be firmware version 2020-07-08, which is also the latest version available from the repository here (as of now):

http://toykeeper.net/torches/fsm/?C=M;O=D

I didn't try to reflash the firmware since it's already the latest version.

I was testing the flashlight. I've done a factory reset, configured temperature properly (as I always do when getting an Anduril based flashlight).

Now testing the strobes modes, I notice something weird:

  • candle mode, lightning mode, tactical strobe works normally.
  • bike flash mode appears to be "a bit too bright" for me but is still OK (normally, I notice that the bike-flash constant brightness is not too dim nor too bright, but in this case, the constant light is quite bright, and the "flash" is just barely brighter than the constant light)
  • however the weirdness is with the "party strobe" (adjustable speed strobe) mode -- the light is very very dim (at first I thought the light had turned off, but noticed that indeed it is doing sort of the "party strobe" mode but at very dim brightness level.

What might be the issue here?

You can change the brightness with 1H / 2H like in normal ramp.

Sadly this is “normal” with the KR4 driver. The output is not able to turn on fast enough. The on-time was already increased, but this might not be enough. You’ll see the same with the zero blink in battcheck mode which is way too dark.

Mine was doing the same thing. There is a flag in the cfg file that changes the party strobe timing for the KR4 driver since it can’t handle the faster pulse rate.
Initially, the D4V2 E21A (using the KR4 driver) had its own config file, and was called the D4V2.5. I went back and found the old revision of that cfg file and it appears the flag in question wasn’t enabled. That’s probably why ours don’t work correctly.

Now that D4V2.5 and KR4 have been merged, it appears the flag is set correctly. I believe you should be able to flash the latest KR4-nofet firmware (anduril.2020-04-27.noctigon-kr4-nofet.hex) located here and it should fix the problem. I compiled it myself, and it works fine. Just make sure you use the nofet build. The E21A apparently can’t tolerate the FET.

For reference, the cfg file for the D4V2 E21A is cfg-noctigon-kr4-nofet.h . However, the flag in question is in cfg-noctigon-kr4.h (lines 52 & 53) which is referenced from the nofet config file.

Hopefully, this makes sense.

Thanks for the explanation, SammysHP and trakcon for verifying the 2020-04-27 kr4-nofet doesn’t have this issue (I tested the 2020-04-27 which has the party strobe work properly).

I assume the “2020-07-08 d4v2.5-nofet” is a later revision, so it must have newer fixes, but it looks like the earlier 2020-04-27 kr4-nofet didn’t have this bug.

(I’m not knowledgeable enough, or didn’t try to invest time to try compiling my own hex files, so I just use the hex files in the repository pointed above — I check the repository once in a while).

The Anduril 2 hex file repository appears to be available in the similar link above — maybe I’ll try Anduril 2 on the D4v2 with EA21 LED.

I see there are the D4v2-NoFET and KR4-NoFET hex file — any idea which will be better for the D4v2 with EA21 LED? I’m guessing to use the KR4-NoFET, would that be right?

You’re welcome! Yes, the kr4-nofet is correct.