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. 
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
Hi guys! I’m new to Narsil, just got a BLF Q8 and have a question. While in ramping, when the main light is clicked on, the indicator switch blinks sometimes once whereas sometimes it blinks twice. What does 1 blink versus 2 blinks mean? Also, right after I ramp the light up or down it will blink once or twice as well. It seems to blink only once if the output is on the low spectrum and twice for the higher spectrum.
Oh and another simple one, when the head is loosened and then tightened, the light blinks 2 times, is there any significance or is just letting me know it’s made contact?
Thanks!
1 blink: moon to ~160 lumens (maximum level for the 7135 current regulation chip).
2 blinks: Above ~160 lumens (direct-drive FET is engaged).
2 blinks when turning on: Just lets the user know power is connected.
Awesome thanks a lot!
I tried to use the ramp to 80% for normal 3 Channel output
but it is notworking
turbo is very low almost like moonlight
P.S.
I added turbo after the last used mode and it works
so ramp size is 140 and 141 value is turbo
Does someone have instructions how to compile narsilm 1.2 under linux? the Makefile seems to be prepared for windows only…
Edit: figured it out. Will create repository for linux later.
Sorry for the late response… I normally just use the bin/build-85.sh script in my firmware repository. It seems to work fine on NarsilM. I think v1.2 may have had a typo on one of the #include lines though, a capitalization issue, which made it throw an error.
I initally started out using Makefiles in the repository, but almost every project uses the same build and flash commands and I got sick of trying to keep all the Makefiles in sync. So now it mostly uses shared build scripts instead.
I discovered today an odd behavior on the GT v1.2
The driver starts to step down at about 3.45V cell voltage, not sure why, in the tkcalwright is written 3.1V
thermal and cell voltage readout shows no error
How can I change the ramping speed in v1.2?
And is a voltage divider the only option for battery voltage sensing? Or can it compare the VCC input voltage with the internal reference as well?
The ramping goes at 62 fps, with 150 total steps. To change the speed you could either make it go at two/three/four frames per step, or change the number of steps in the ramp table.
It should be able to measure voltage either through a divider or direct on the VCC pin, by setting the relevant option in the code. I don’t recall what the #define for that is though.