NarsilM - configurable e-switch firmware for Multi channels, v1.3

Yes, all the other settings survive battery changes, including the timed step-downs.

According to my shared NarsilM builds/releases here on a google drive share, S43 and the original FT03 is using v1.1. Dunno - the new blue FT03 XHP50.2 I have right now in my hand blinks out v1.3.

I'm pretty sure the GT Mini went out with a "good" v1.3 that originated from me.

This doesnt sound like the bug that doesnt remember settings, not if it’s just the one thermal setting that it can’t remember. The memory bug I’ve heard people talk about basically didn’t remember any changes.

Did it actually remember the temperature setting and only loose it after disconnecting power or did it not remember at all?

(The S43 is a bit unique because it can heat up so darn fast. The key is make sure it’s not already warm on the inside when you go to set the thermal limit. I make sure it’s not been used for an hour at least, then I use a fully charged cell and run the thermal test. This works everytime on my Narsil lights. Some people use the light previously and it gets warm inside and they don’t think about it, then they set the temp limit and it ends up being off.)

I can’t say for sure what the issue is, but it sounds exactly like the old memory bug. It would forget things at random… even just one or two things. The reason it was initially found was because Hank of Emisar noticed that the D4 prototypes would sometimes forget their thermal configuration. Then later it was discovered that a different old Narsil light would sometimes forget things too.

So I rewrote that part of the code for Emisar, and sent Tom info about the issue including a patch. He fixed NarsilM, and since then, the issue hasn’t come up much.

It was really easy to miss since it usually worked, it was only noticeable after a battery change, and it generally only forgot a little bit at a time when it failed. If I recall correctly, lots of people used it happily for more than a year before anyone noticed.

For the S43’s…

Yes, it remembers the temperature setting as long as I don’t disconnect the battery. If I use the micro-USB to recharge, then no problem. If I take the battery out to recharge it, then it reverts back to the default temperature setting (which is too low, IMO).

All other settings are remembered across battery changes, at least the ones I’ve reprogrammed (maybe half-a-dozen of them).

I thought maybe it was a safety thing or something. But since I can turn off temperature step-down entirely, and it is remembered, I presume not.

Oh boy, I forget more than I can remember (I was born in '57...) - but I do recall something of this, just not exactly what the change/bug was? TK - do you recall? Thought it had to do with interrupts maybe?

I changed two things. I’m not sure which one actually fixed it, or if it was both together. Those two things were: Turning interrupts off during eeprom access, and using the library functions.

Ok - will check - don't think I made the change though in v1.3

What about BLF Q8 NarsilM V1.3 ? :smiley:

Sorry, I haven't been keeping up with this thread for a long time. I just updated the OP. Over the last couple weeks I'm getting bombarded with emails from the google drive service to grant individuals permission to access various Narsil and NarsilM files, mostly the manuals. Apparently google has updated their links to increase security and made the old links broken/obsolete, but they allow the requestor to get an updated link from the publisher individually.

So, I updated all the link in the OP. Unfortunately I don't know where people are clicking on my google drive share links, but if they are coming from here on joechina's thread cheat thread, I can't update those links - only joechina can and he hasn't been on for 2 1/2 months I'll post there and pm him. When I get a chance, I'll look around further. Thought there was a NarsilM V1.3 manual somewhere - can't find it, but really there was no changes effecting the manual in v1.3 or v1.2 (probably v1.1 as well).

It's been here: HEX file of NarsilM v1.3 for the Q8

Thanks for the link.

I remember flashing my BLF Q8 from the default v1.0 (which had more difficult button-press to change strobe modes) to v1.2 (likely from your firmware repository way back 2018, which is the file date-time stamp of the NarsilM-Q8.hex file I got (v1.2) which I flashed on my BLF Q8.

Haven’t realized there is a v1.3 NarsilM for BLF Q8.

Any idea what’s the difference of NarsilM v1.3 from v1.2?

I seem to recall that v1.2 changed how strobe modes is accessed (easier to switch strobe on v1.2 than on v1.0).
While v1.3 seems to have changed the waiting time (hold down button) for settings configuration (from 8 seconds to 16 seconds?)

In OP?

Hi, I have a question about NarsilM in combination with the temperature controller.

I am testing the GT94X and I found the following:

  1. I tested with default settings, the light turns down from Turbo to an output below 500 lumens, and runs for couple of hours, without increasing brightness again. The batteries were still 3.7V after 1 hour.
  2. I then set the max temperature myself (In the 3rd configuration menu: Auto step-down) and set the max temp to about 60 degrees, then turned the light off). I then ran the runtime test again, at around 60 degrees it dropped output, but never increased brightness again. The light continues to run for hours below 500 lumens and the body of the flashlight is eventually about the same as the ambient temperature. The batteries were 3.x V after 2-3 hours.

What could be going on here?

  1. Is the temperature controller only used to drop output, but not maintain its brightness at the highest output possible below the set Max temperature?

I don’t believe Narsil can increase output after lowering it. That is something Anduril can do.

Interesting.

Do you know what setting is used for 'after' the output drop?

500 lumens (actually lower than that) seems to be a bit on the conservative side for such a big light :D

NarsilM does not have a PID control algorithm or anything equivalent, so yes - it doesn't raise the output, only drops.

As far as I know, NarsilM does not consider the light it's running in for temp regulation and has no calibration based on the light, so it settled to 500 lumens purely by the common temp regulation algorithm it uses. I don't think TA could have tweaked that area specifically for the GT94. Could have been possible to do so, but the effort would be significant.

Thank you for the explanation! Appreciate that. I thought mine was broken :D

Hello everyone… I’m new to this topic, but I’ve been reading it for a long time, and I need help.
I am building a head light, and I really like the narsil firmware, I have modified it to have SOS and the battery test to indicate the percentage. I need to increase the brightness level in the battery check mode, I just need that, that the led shines more when it is giving me the information,
does anyone know where it changes??? please it’s been 1 month and I don’t see it
Thank you.
Thank you all, I found where it is…
in case someone can help,
in the ModeSet.h tab,
#define BLINK_BRIGHTNESS 200.0

Yes, I see it there, can confirm that.