The e21a and mule arent released yet, there is sst20 and xpl hi currently
We have managed to put 16 pcs E21 LED into the KR4 MCPCB as a mule.
16 E21s…now that’s tempting. Will you be using a buck driver for it?
If TK’s sustainable output test is actually of the 95 cri sst20…That’s amazing!
It will use 4*E21 LEDs, with carclo 10622/10623 optic.
No, the sizes are not the same. The FW clip is too small.
It is not really like anything else… it’s kind of a new thing entirely, which combines the good parts of several other lights. It’s smaller than a D4S but offers similar performance. It’s regulated and more efficient like the K1, but adds direct-drive for bursts of turbo. It has a tail switch like a FW3A, but is more robust. It has the features and beam profile of a D4, but is more refined.
There is no PWM below 5 Amps. It has no amc7135 chips. With default settings, it has no PWM on any level, since the ramp ceiling is set at 5 A and the next step up is turbo (direct-drive). It is only between those two levels that any PWM is used, but the ramp doesn’t go there unless the user reconfigures it.
Yes, it seems to get more efficient as voltage drops. As for overall efficiency, if my runtime tests are accurate, it seems to be about 20% more efficient than a D4. At least, I tested both with the same exact battery, and the KR4 had 20% more area under the curve. It is possible that I made a measurement error, but it’s definitely more efficient and the question is mostly a matter of how much. Maybe it’s only 10% or 15% more efficient.
The only code I’ve ported to this driver is Anduril, so I doubt it will have any other stock firmware options.
However, even though you hate Anduril, you are in luck. It is open-source and uses the FSM UI toolkit, so you can make whatever interface you want. There are a few example UIs to start from, too… ZebraLight, Olight, Werner’s UI, and two simplified versions of Anduril, plus compile-time options to enable/disable many of the features… and sort of a guide for how to make your own.
If you can represent the UI you want in the form of a flowchart, or as a list of states and the button events which move between states, it should be pretty straightforward to create. Just make sure to get a flashing kit with it, and then it can have any interface you want.
I’m confused too. It’s definitely SST-20, and it looks like 4000K, but it’s performing like a low-CRI version instead of a high-CRI version. It’d be nice to get some confirmation on what it actually is.
It’s hard for me to gauge the CCT of SST-20 LEDs, because they all look yellow-green to me. However, the beam looks almost identical to another SST-20 4000K 95CRI light I have, and looks similar to a XP-L 4000K, and does not look like any 4500K or 5000K lights I’ve compared it against.
But in my calibrated lumen tube, I’m seeing numbers way higher than a high-CRI SST-20 should be capable of. Even with an old cell from 2014, it’s measuring 3840 lm at start. With a newer cell, I got 4044 lm. So I’m not sure what’s going on. It shouldn’t be able to do that.
FWIW, the way I scaled the runtime graph was: I turned the light on at its default level and measured it in my light tube. It came out to 197 lm. Then I moved the light into position for runtime testing, started the test, let it run a few seconds, then double-clicked for turbo. Afterward, I scaled the graph so the first few seconds hit exactly 197 lm.
If you look at anything brown you can clearly tell the difference between 70 and 95 cri. With low cri it will look yellow/green.
I’m in for an E21a version if it uses a buck or boost driver 
I think the E21a under those optics will be amazing. Much better intensity over the other larger LED’s.
It’s 5A constant linear driver, without direct drive.
TK WROTE
QUOTE. The only code I’ve ported to this driver is Anduril, so I doubt it will have any other stock firmware options.
However, even though you hate Anduril, you are in luck. It is open-source and uses the FSM UI toolkit, so you can make whatever interface you want. There are a few example UIs to start from, too… ZebraLight, Olight, Werner’s UI, and two simplified versions of Anduril, plus compile-time options to enable/disable many of the features… and sort of a guide for how to make your own.
If you can represent the UI you want in the form of a flowchart, or as a list of states and the button events which move between states, it should be pretty straightforward to create. Just make sure to get a flashing kit with it, and then it can have any interface QUOTE.
That would be a NO then ,
Ok that’s not a flashlight for me ,I think I’ll leave it .
Thank you.
I love Anduril and Noctigon/Emisar, perfect combination!
Thx TK for clarification. Was about to pull the trigger but the more i look at that clip the more seems to me someone took it from no name Aliexpress light and put it on Noctigon...
I’ll wait for E21 or maybe TiCu (if any at all), not to think about that clip.
True, it makes things look yellow/green. But so does high-CRI SST-20. However, I tried some other color tests… Mystery SST-20 vs FA3 SST-20 (4000K, 95 CRI).
On a white wall, both look very similar. Both are yellow-green, but the mystery SST-20 looks slightly more yellow-green.
Shining at a bright red object, both look good but the FA3 looks more vibrant.
Shining at a pink/magenta object, the mystery SST shows pretty accurate color while the FA3 sucks the blue out and makes it look like a salmon color.
Shining at blue objects, the mystery SST looks blue but the FA3 looks sort of sea-green.
So they’re definitely different. The mystery SST has weaker red and stronger blue rendering, which suggests lower CRI and/or higher CCT… but aside from the white wall comparison (where the mystery light looks warmer), it looks like it produces more accurate colors than the high-CRI FA3.
Once I’m done testing everything, I may just add a minus-green filter to it and run a no-FET version of the firmware. It looks pretty decent after adding that, and doesn’t suck the blue out of things like my FA3 does.
Or I could order a XP-L HI 5000K version. Those always look good.
Wow, that’s heavy. 25 g more than already heavy D4 (gen 1)? It is about as large as FW21 and actually weighs more, even with cell inside. I appreciate innovation and I’m very curious about the efficiency but it’s not as space-efficient as I would hope for.
I don’t know if this is news or not, but Hank now has J5 output bin SST20s in HB4 FB4 tint. I’d assume that’s what is in the KR4
As for the E21A version, I’d hold off until there is a buck or boost driver available. Maybe loneoceans could work with Hank and adapt his new lume1 driver for this?
Very interested and excited for the E21A MCPCBs though. Will you offer these as components?
A series quad E21A would be a perfect application for a 12v boost driver.
A mule allows for a shorter flashlight (no optic), will the mule version be shorter?
No, the host is the same length, because we are improving thermal mass that way.
wanting to get one but Australian borders are all closed. It will be a long wait until this corona virus is over 
Im sure most other countries are in same situation.
As far as I know, the cargo will enter into Austranlian board without problems?