Emisar D4S review

Awk is an ancient programming language created for processing text files. A very short awk program can do some tasks that would take pages in C or Java.

… and anything longer than a very short Awk program is usually best written in some other language. It’s only really good for one-liners these days.

awk is magic indeed

Maximum battery length that D4S will accept is 69mm, according to specs, if that helps.
The length of that KeepPower cell on that 18650.uk site is listed as 60.3mm, which is obviously wrong.

I still like Droid48 when I’m not at a computer for a quick calculation.

My 11C got me through my senior year of HS, and all of college. As an “accepted into grad school” gift to myself I bought a 48G, and I just barely used it enough to get accustomed to the UI.

Anyone still have a functioning Bomar Brain?

Those Casios with the miniature Nixie tube display were just great. Apart from battery life. They also had a couple of Easter-Eggs embedded too. If I could remember the keystrokes I’d tell you.

A proper HP has a proper red LED display, sadly my best one is bust, I think the Eprom just faded away. Perhaps because it was kept beside several, properly enclosed, radiation sources :person_facepalming:

Something worth noting for those who assume that e.g. Flash memory is magically permanent, it’s really just a few (very few nowadays) electrons, captured in a few thousand, or hundred, molecules of SiO2. Amazing that it works at-all.

Nevertheless all my important devices have been upgraded to SSD (good ones) and the slow spinning rust is kept for cold storage.

Will your torches with microcontrollers still work in e.g. 20 or 30 years time ? Maybe, maybe not. I do have a few with purely analogue, discrete component drivers, which could be eternal, but I’ll probably be dead before I find out.

There was a bug on the first batch of Convoy’s new drivers which, after calculating the scale of the chips involved, worked out to having a few hundred atoms flipped the wrong way. Basically, the SRAM decays to its default state when power is removed, and that state depends on the orientation of the atoms in the SRAM memory cells. If a few specific bits had enough atoms rotated in the less-popular direction, it would decay to a value which caused problems.

So people returned products for refund or replacement, and justifiably so. Because, totally at random, if they were unlucky enough to have a few hundred atoms out of place, it didn’t work right.

As soon as we discovered the issue, I updated the code to take a larger sample, which dramatically reduces the chance of that happening. But due to the nature of these things, the chance is still non-zero.

No need for concern for yall tho …. that 1 in a million is reserved for me :person_facepalming:

I think the following tiny bug has not been mentioned before.
My D4S Nichia does not always save moonlight into memory.

Procedure to replicate: Light is off. Unscrew and screw again the tailcap to reset memory. Click and hold to start at moonlight. Release quick enough before (!) it starts ramping. Let it on as long as you wish. Switch off by a single click. Switch on again with a single click. Now the light starts at the power level from the reset state (when tailcap was screwed).

It actually just doesn’t save moonlight into memory with the above mentioned procedure. So the light might even start in turbo if that is the last used level.
If you just have the light on and ramp it fully down to moonlight, the level will be saved into memory flawlessly.

Maybe it’s just my model or maybe it’s not a bug, but a feature? :slight_smile:

Nonetheless great UI and a great Light. Loving it :slight_smile:

Try either holding it down longer or ramping up slightly then back down.
If it’s important that you absolutely start on moonlight just hold down the button a microsecond longer rather than clicking it. Pretty simple.
If it happens to go up a level then click click/hold to force it to ramp downward.

Yea, thank you. I do this workaround already. Just wanted to mention this behavior so it is recognized and can be fixed in future UI revisions

Indeed, that is not a bug. It was added on purpose because people wanted it. The memory only remembers the last level the user ramped to. Going to a level via shortcut, like moon-from-off or double-click-for-max, does not change the memorized level.

To make it remember a level, including moon, the user must ramp to it instead of using a shortcut.

That explains it. Thanks :slight_smile:

Thank you sir. I end up ordering two golisi l2 from banggood for $13.69 each.

If anyone need a link, please let me know… i was told there were some fake golisi charger out there.

In smooth ramp mode, is there supposed to be a little ‘hiccup’ somewhere half way through the ramp? By hiccup I mean a brief hesitation where it seems like the light shuts off for a split second and comes back on at a higher level, and then continues ramping up from there?

Also, I realized the Shockli cell doesn’t make contact with the terminals of my Miboxer C4-12. So now I’m stuck using the “slow” Lii-500 to charge it. Sigh.

I use the MiBoxer C4-12 to recharge my Shockli’s all the time…. check the negative terminal of your charger, you might have to bend it forward a bit so it stands straight up…

I use mine to charge 32650’s as well. :wink:

Thanks for the tip. Looks like this helped!

Isnt that hiccup when it goes from regulated to unregulated?

Yes. That marks where the light switches from 7135 to 7135+FET.