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

So when the user needs battcheck you shut it off?
That’s like the range calculator in my RENAULT. It goes down till 80km than its dead. o_O
I don’t need a value for range when the gas tank is full. I need it when I want to know can I reach the gas station 15km away.

The idea is to avoid over-discharging the cells, since if they get too low they can be permanently damaged or destroyed.

It’ll blink out voltage until it drops below 2.9V (about 99.9% empty), and then it shuts off. It’d be like if your Renault gave estimates down to 0.5km before it shut off the engine to avoid damaging the fuel tank.

If the user turns it back on, it’ll blink out voltage again, but may shut off after 6+ seconds if the voltage stays low.

Thats better than my Renault if you get a reading when you start the light / engine.
:slight_smile:

I got a guy reporting, that if NarsilM is set to Turbo when powering on that with thermal stepdown enabled the light steps down after half a second

Here are the videos. I set my camera to have ISO and shutter speed locked. This is while turning the light on from the tail cap. It behaves normally when turning on the light via the front button.

With thermal stepdown disabled (no visible drop in light.)

With thermal stepdown enabled (sharp drop after about 1/2 second).

Lexcel
which version of NarsilM?
Version 1.2 has a bug fix for step down, but I don’t know of the head if that fits to your case.

That driver was 1.0

Did he adjust the thermal temp accurately? About how long did he set the light to step down?

Maybe he programmed it to step down at 30°C instead of a normal 50-60?

Tom, I was just now able to finally flash the new firmware to the BLF GT. The change to tactical mode is a nice improvement. This is the only E switch firmware I’ve ever used that could actually be used to tap out morse code. That is so awesome. I love having the battery disconnect be your way out. It seems to work perfectly.

I have one question. Where you said on the update sheet “make click&hold in MODES or STROBES wrap from 1st mode to last.” I am a little confused about what result I’m supposed to be getting here. Can you give me a second example. Say one where the strobes are enabled?

I believe he is talking about mode cycling. When selecting your desired mode one will normally click to advance through the group. When the last mode in the group is reached the next click cycles back to first mode and this continues till one pauses greater than 1.2secs to lock in that mode. The described “wrap from 1st mode to last” then just means that the same will happed with clock&hold but in reverse. Cycling back through the modes will bring you from the first mode to the last mode and then down through the modes as long as the user continues to do a clock&hold. When in strobes, same thing. Going backwards in stones will go from the first strobe directly to the last with a clock&hold.

Does this help? I believe this is what he’s saying anyway…

^ Yes. On NarsilM v1 lets say you go to strobes and stop on the 3rd one, bike strobe. Once it’s locked in, one click goes to off. If you press and hold it goes back to strobe 2 which is the tactical strobe. If you press and hold again it goes back to strobe 1 which is the constant rate strobe. If you press and hold again the light goes off.

In NarsilM v1.2, if you press and hold from strobe 1 it will now go to strobe 5 (10 sec beacon) instead of off.

Some folks had trouble going to the different strobe modes. They would get into the first strobe then get stuck. They couldn’t go forward to the 2nd or 3rd etc… Now they can.

The same should be true for mode sets. When you use the press and hold to go down to the first level you get stuck. Another press and hold would turn the light off. Now it should allow you to keep cycling through all the modes.

Does that make sense?

What LightRider and JasonWW said.

You have 5 strobe modes (#1 to #5)
In v1.0 you can only navigate in the borders from #1 to #5. If you go from #1 backwards you switch the lamp off. Or if you go from #5 forward.

In v1.2 you can go backwards from #1 to #5.
So you can search the right strobe endlessly going backwards.

The navigation in STROBES and MODES is the same.
Edit: I shouldn’t write about MODES without checking
The reason why foreward revolving is not there:
When you switch your MODES brighter and brighter you normally want to go to MAXIMUM. This way it stops there.
If you want to go to MOON, switch it off and on.

Thanks gang. I understand now. Where I got lost is at Click&Hold. I was thinking he meant hold continuously, but it’s referring to the 1/3 second press.

That said ever thing I have tested about the UI (which is a lot) works perfectly in the GT :slight_smile:

Click and hold (till the mode changes) :wink:

In mode sets, when you cycle up the brightness levels, does it stop at the brightest level or does the light turn off (like in the old version) or does it wrap around back to the lowest level?

sorry, I probably wrote BS about stopping.

Yes, No 10%

Only 25、50%

Okay, it’s still a glitch due to the driver being 3 channel.

@Tom
I have a new cheat sheet for the GT under http://bit.ly/narsil-cs

I don’t know if the mode table is right.
Can you please check?
I didn’t found a manual for the GT. I added notes from the Q8 feedback. Maybe that can be used in a GT manual?

Joe

BLF-GT user manual V1.2 draft

Link below:

BLF-GT user manual draft12.pdf

I found that in v1.2 the 2S cant be build as in the Narsil.c the line with
tk-calibWight.h
is commented out so it gets build errors missing the #define ADC_22…44

I looked through this. It is very well written, but I wanted to make some notes on it.

1. There is no mention that the ramping mode only goes to 75? (whatever 2A at the emitter is considered) and a dbl click to turbo is the only way to get to full power (100).

2. On the beginning of page 2 I feel it should be pointed out that after the 8 seconds, and entering the config menu, it should be noted that the first 2 blinks are to be ignored and are just to get you ready to count. This confuses a lot of people. Always ignore the first 2 blinks and only count the blanks after it.

Who wrote this up? They did a good job.