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

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.

Thanks JasonWW!

Jacques wrote it, I did prove readings.
We went from draft 3 on Friday to draft 12 on Monday morning.

We don’t know Tom’s opinion about this and hope he is fine with it. But we couldn’t get him.

There is the first sentence on page 3 and on page 5. Yes it would be clearer with “count the …”

Ooops, I was counting the pdf pages and not the page numbers printed on the document. Top of page 5 is what I meant.

I somehow read right past the top of page 3 where it says ramping goes to 80%.

Looks good.

Does someone has compiled Narsil hex file for 3 channel TA driver with 2S battery config and lower ramping top than turbo like in the GT firmware? I built an Convoy L6 XHP70.2 today and I want the ramping top at about 3000 lumens because the light can handle the heat from that output. Currently it puts out 7800 lumens and gets hot fast. But with ramping I can’t really feel with my eye that level where the 3K lumens are to stop there.

Hmm, 2S plus 7135 chips is still a bit risky since the chips tend to fry. Did anyone ever try those higher-voltage 7135 chips? It’d be awfully nice to have a simple current-control PWM chip for serial-cell drivers.

Otherwise, it should be possible to generate a 2S ramp by dividing the values to keep the chips under a safe limit. Not sure what that limit is though; maybe I have info on it somewhere… Looking at one of RMM’s builds, I see a limit of 37/255 for 2S. He turns the 7135 chip off for FET modes though, so it might have a bump in the ramp. This is all a bit fiddly.

Haikelite is about to release a light with a driver that is a Texas Avenger derivative and uses 12V LEDs.
Either they went as far as to make it a FET-only driver or they can show us 7135-like chips that work. :wink:

in 2S its not the voltage that is killing the AMCs its a dynamic reaction of the FET hard on/off while the AMCs gate is active that kills them, DEL added 2 caps that should fix this quite successful on currents up to 20A

7135 pin compatible chips are availiable, but they have problems with Moonlight modes you need to reduce PWM frequency for them or change the coder for longer on Cycle

Ah, interesting. I should probably look at multi-cell stuff more often…

I wonder how moon would look. I’ve taken to reducing the PWM frequency on the lowest modes lately, which should at least help somewhat with the issue described. Most modes run at 8 MHz, but when it gets low enough I cut the clock speed in half, then at the bottom of the ramp I cut it in half again. This makes moon more efficient, more stable, and less hardware-sensitive.

On my yesterday built L6 is pretty low! Almost can’t see it.

At super-low levels like that, I found I was seeing like 6 mA power use — 5.5 mA to run the MCU and 0.5 to run the LED. By underclocking the MCU and using idle states, I got moon down to about 1.7 mA, even though the bottom level is putting out somewhat more light. It’s probably like 1.0 mA for the MCU and 0.7 mA for the LED. I haven’t been able to try it on a higher-voltage light though, and I expect the behavior might be different.

Is it possible to get on those newer Buck and Boost drivers to use the free pads to use NTC thermistor on an unsued input

I also get frequently requests on dual e-switch input, or even triple, just something like safe current mode to this extra button by click and hold it for 3 seconds or so