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

[steel_1024]

Is it possible to (Compile) and (Assemble) a NarsilMv10-31s.hex?

Put it on the OP link.

I wish mod a Manker U11 (4 LED)(side switch)

[RotorHead64]

@RotorHead64

@Tom E

@Lexel

@Tom E

Ooops, probably definite you have to change the initialization code right in the beginning of main(). Critical initialization of ports for I/O and PWM’s is there.

I dont understand how to do that

Ok, find this code in main:

  #if OUT_CHANNELS == 3    // Triple Channel
   // Second PWM counter is ... weird (straight from bistro-tripledown.c)
   TCCR1 = _BV (CS10);
   GTCCR = _BV (COM1B1) | _BV (PWM1B);
   OCR1C = 255;  // Set ceiling value to maximum
  #endif

Comment out the #if and #endif, so the code is executed. That looks like the only change you need to make in main(). This enables PWM on pin #3 I believe, which you need.

So, we got the normal 3 channel TA board working as a 2 channel FET+1 with 1 cell.

Now, what would need to be done to get the TA 20-30mm LDO board to work as a 1 channel FET only 2s+ cells?

I have the 30mm TA LDO built. I'm using the MIC5235-5.0YM5 LDO with R1 of 360k and R2 at 47k, C1 and C2 at 10uf, R3 100k, R4 47 ohm, R5 4.7 ohm, R6 0 ohm jumper, R7 0 ohm jumper, D1 nothing ? , SIR800 FET, and Attiny85V 10SU.

Is the D1 Schottky required with the LDO 2s?

I reassigned the pins in the RegisterSettings.h, made the change in the main() to enable PWM on pin 3, used the Setups-1Chan.h, un commented #define USING_360K, commented out the #define D1_DIODE 2. Fuses are lfuse 0xE2, hfuse 0xDE, efuse 0xff.

When I connect power to the driver, 2s connected to an MTG2, the led erratically flickers for several seconds until it finally blinks 2wice and stops for awhile. It'll ramp up and down, do turbo, bat check, strobes and then all of a sudden it's doing its own thing. It'll ramp to max on its own and I'm unable to shut it off or anything else with the e switch. Sometimes it works but most of the time it's Psycho!

I've swapped the caps, MCU and the FET. I've tried a few different things with the firmware but it's always the same

I'm sure there's something super simple I'm missing. Please help...

So I figured this out. For some reason the switch pin on the MCU was malfunctioning. I was poking around with the dmm and noticed there was 21k ohm from the switch pin to ground. I thought maybe the eswitch was the source but after some more troubleshooting I removed the MCU and measured from the ground pin to the switch pin and it was 21k ohm. A new unused MCU measured several mega ohms. After swapping the MCU it works...

[b1i1l1l1y1]

I think this was discussed in the Q8 thread but that moves so darn fast it’s well buried by now and can’t find it.

Is there an easy way or shortcut to 100% 7135 while in ramping mode? Only way I know of is to yo-yo between 1 and 2 button blinks to indicate 7135 or fet

[joechina]

To my knowledge there is no Shortcut to full 7135 in NarsilM v1.0.

The Emisar lamps have one.

[joechina]

Hello Tom I posted in the Q8 Mod thread, but I think it belongs here

Hello, how does the switch blink when the batteries run low at 3V?

What I’ve written down:
Low Voltage Protection (LVP)
@3V
Main LED: 3x blinks as indication
Indicator LED: blinks every 8 sec

What my Q8 does:
Main LED blinks three times.
The indicator LED goes on, than off and stays on.
And it goes off with the next brightness change: 3x blinks of the main LED, switch LED off.

Edit:
It seems also every second try the switch LED turns not on

Weird next try:
1th stepdown
Main: 3x blinks
Switch: 1x blink, ON

immediately after this comes the
2th stepdown
Main: 3x blinks
Switch: 1x blink, ON

Manual off and ramp to max

1th stepdown
Main: 3x blinks
Switch: 1x blink, OFF

immediately after this comes the
2th stepdown
Main: 3x blinks
Switch: 1x blink, ON

[Tom_E]

Sorry, haven't been able to keep up with this thread - will try from now on. Thanks TK for the help and support! Lots of things goin on with the Q8's.

One more BUG added, thanks to joechina... that's a good thing that he found it, I think . Really haven't been able to spend any time on firmware lately. For some reason I keep playing VOB's youtube review of the BLF GT over and over again, featured here on REDDIT. The 5:00 to 6:00 section features NarsilM - my favorite part .

Here's the latest Open Issues:

Open Issues
-----------
- 2017/10/04: BUG: in LVP switch LED control: the LED sometimes is left on after an LVP drop,
and is not blinking the way it should be. The "bug" is that I'm trying to control the
switch LEDs from multiple places so it's getting turned off quickly after turned on, and
left on when it should be left off. It's a timing thing, so has sort of a random
pattern - sometimes left on, sometimes left off.
The 8 sec LVP blink need to be qualified better, and should not be calling Setlevel() as is
because it wants to control the LED

- 2017/10/01: temp stepdown should not happen right away from turn ON. Delay it, least by
15 seconds!

- 2017/09/29: BUG: for temperature stepdown, where in moon mode, a temp stepdown is
actually done because moon mode is marked as special level 255, which is considerred as a
high level of output instead of very low. The stepdown results in the light switching much
brighter. This should only happen id the temperature threshold is set to a low temp, or the
light is still hot and not cooled down when moon mode is chosen. It can also result in an
immediate jump to the stepdown level as soon as the light is turned on in moon mode. Might
appear as a bright flash when ramping first starts.

- re-work triple channel ramping tables: add more to the FET range, check/test for different
# of 7135's in the bank (5/27: not sure this is necessary now with new 3 chan ramping table)

- (from JasonWWW) triple channel mode sets are not completely defined, and are different than 2
chans - need to, at a minimum, document it this way
- (from JasonWWW) possible problem with mode memory in 3 chan config - must check it out

Possible New Features
---------------------
- besides supporting turbo/max on power up, add support if powered up with the button pressed,
come up in moon (lowest) mode
- joechina recommended to do a quick ramp to max, maybe even quick fade to OFF to ease tension to
the eyes. The Olight A1R does this.
- enhancing tailswitch support: full mode sets w/memory (Lexel)
- add ability to have timed and temp step down simultaneously (Lexel)
- research "bump protection" - tolerate a short loss of power
- build in a method to show the current config settings
- more blinky modes, like lightning, campfire, etc.

Done Issues/Features
- FIXED: Tom E: in mode sets, step down settings wasn't working correctly
- FIXED: 1 Lexel/BLF spotted: Blinkies unable to turn off in ramping
- FIXED: delay processing of fast click operations to avoid max/turbo flash and allow more fast
click options (over 4 doesn't work)
- DONE: add in buck driver support cleanly (BLF GT)
- DONE: add momentary/tactical mode

[MRsDNF]

Thanks for the work Tom. :+1:

[vestureofblood]

Tom for the BLF GT in batt check mode is the voltage blinked out per cell? Not blinked out for 16v 4s pack? 4 blinks, a pause then 2 blinks means I have 4.2V per cell?

[Tom_E]

Right. Yes, it's measuring 4S coming in, but displaying on a per cell basic. DEL did all the work there to get it right with proper resistor values, then wrote the code for measuring it, etc. He took Narsil and fuly modded it to support the driver, then later, I ported and combined it into one NarsilM version, so buck driver support is now melded in with the 1, 2, and 3 channel support in NarsilM.

Ohhh - did the 5X click for tactical mode work?

[JasonWW]

@vestureofblood

Tom for the BLF GT in batt check mode is the voltage blinked out per cell? Not blinked out for 16v 4s pack? 4 blinks, a pause then 2 blinks means I have 4.2V per cell?

It usually blinks the per cell voltage. So nothing higher than 4.2.

I’m sure Tom will confirm that when he checks here.

EDIT, That was quick. Lol

[vestureofblood]

Awesome. I actually thing that is a lot better than going off the pack voltage. It keeps things simple. I will probly be hitting you up several
times in the next couple days as I have started my vid on this UI

Are there any other lights besides this and the Q8 that are coming from a factory with this firmware?

Any bullet points you want me to be sure an touch on FAQ etc?

Also when your in the strobe configuration mode I see it says “1=disable, 2=one strobe, 3=all 3 strobe. If I configure it to be ”one strobe” Can I choose which “one” it is?

EDIT: Yes, the tactical mode does work

[JasonWW]

@vestureofblood

Awesome. I actually thing that is a lot better than going off the pack voltage. It keeps things simple. I will probly be hitting you up several
times in the next couple days as I have started my vid on this UI

Are there any other lights besides this and the Q8 that are coming from a factory with this firmware?

Any bullet points you want me to be sure an touch on FAQ etc?

You can check the 6 videos in my sig. They are very basic as I’m not used to making videos. I’m sure yours will look and sound better.

There is so much to cover, you might consider doing more than one video. I’d cover everything that I did, plus what I couldn’t, which is all the indictator light functions.

The Q8 and GT are the first commercial lights with Narsil UI.

The Emisar D1 and D4 are similar, but use a slightly different UI called RampingIOS.

[Tom_E]

Not sure yet but also the FW3A may be launched with NarsilM. Nothing commercial accept for the Emisar, being based on Narsil.

[joechina]

Tom
In strobe modes:
If I go back from #1 strobe the lamp goes off. Can we have revolving strobes? So somebody can go #2,#1, #5, #4 , … in circles.

[Tom_E]

Strobes works exactly the same as normal mode operation, so do you want that for strobes and normal modes?

[joechina]

@vestureofblood

Any bullet points you want me to be sure an touch on FAQ etc?

I got a few PMs and questions about the cheat sheet.
Some people seem to have problems to understand the tables and the manual.

I would point out that the normal operation in RAMPING and MODES is very different.

If you look in the first table of the cheat sheet you will see that only the commands for ON and OFF are the same.
I didn’t expect this. I thought a few commands like turbo and moon are the same.

Some people had a problem to switch OFF, lamp seems not respond to click:
Timing of click for off, hold the switch just a tad too long and the Q8 will not register it as shut down command but treat it as a very short ramp command. Your light is not broken. Please try a very fast and short click.

People did asked for examples with complete click-ology.
Best would be to have a lot of subtitles in the video.

Reset to factory in RAMPING:
3x, 2x, 2x, press&hold (for 1.2sec) till 4 blinks

Reset to factory in MODES:
1x, click&hold (for 2.5 sec), 2x, 2x, press&hold (for 1.2sec) till 4 blinks

Switch from MODES to RAMPING
(while holding, the lamp goes into strobes, that’s normal)
hold for 3.2sec, after two short blinks and one blink, 2x.
The lamp continues to blink out configuration for RAMPING.

Switch from RAMPING to MODES
(you hold for a long time, please ramp down, it’s easier on the eyes)
hold for 8sec, after two short blinks and one blink, 1x.
The lamp continues to blink out configuration for MODES.

Strobe Modes:
The normal way (RAMPING: 2x, 2x, Y clicks [Y= 1…4] ) is time sensitive because of the lock in modes. And I got PMs people are not quick enough for the Y clicks, because the Y have to be done right after the second double click.
If navigation is hard, try:

RAMPING from off/on:
Double click, double click, 4 clicks in a row. Now you are in the 5th strobe = 10 sec beacon.

MODES from off/on:
Longhold (over 1,2sec), 4 clicks in a row. Now you are in the 5th strobe

Now you can go back via click&hold. You can go back 4 times, then comes OFF.
If you go backwards you have time to do this.

For RAMPING:
If you want to remember how many clicks to go to B attery = 3 clicks
The B and 3 look quite similar.

Ups, that got lengthy
Sorry Joe

[joechina]

I think yes.

Right now is the navigation in MODES if you go backwards:
Nr2 -> Nr1 -> moon -> OFF -> Turbo -> …

With revolving navigation:
Nr2 -> Nr1 -> moon -> Turbo -> …

Does that any harm?

To be honest I don’t use MODES at all, I can’t tell.

[vestureofblood]

Thank gang. One last question, When your in the strobe configuration mode I see it says “1=disable, 2=one strobe, 3=all 3 strobe. If I configure it to be “one strobe” Can I choose which “one” it is?

[joechina]

As I know, no. When I choose this option it blinks only with strobe #1

Your GT video is greart!

You should do one with the Q8, it’s a verry practical light around the house, its awesome in tailstand, best UI. It’s worth spreading the word.

[Tom_E]

@joechina

“I would point out that the normal operation in RAMPING and MODES is very different.”

That is definitely true. They are completely independent, and intentionally so. RAMPING is based on press&holds to adjust brightness, MODES is based on single clicks to advance to the next mode. The only thing they have in common is the priority given to one click ON, one click OFF, but of course the behavior varies.

For MODES, double clicks (2X, 3X, etc.) are not compatible - there would be too many unintentional actions since you want to be able to fast click through modes. I've used lights with UI's like that and they are a real pain and annoyance. But for RAMPING, double clicks fit in well since your primary means to change brightness is by press&hold.

Like I said, MODES operation and STROBES work exactly the same:

• quick click to next mode
• click&hold to previous mode
• click&hold from the first mode turns the light off (if in MODES, it actually returns to the previous mode)
• the current mode locks in when you stop navigating the modes, and locks in quickly in 1.2 seconds (IDLE_TIME = 75 in the code). You can tweak IDLE_TIME to change this.
• you can easily work around the locked in mode by press&hold to go to previous, then you can advance to the next mode. This will not work if you are on the first strobe mode however, since that will either turn the light off or return to the last mode (if in MODES).

For VOB, if you are used to the old MODES operation of the original Narsil prior to having ramping, then navigating strobes is the same.

If we go with changing the press& hold from 1st mode to loop around to the last mode rather than exiting, I can't think of anything that would cause problems. This would solve the problem for STROBES when you lock in to the first strobe mode, and want to stay in STROBES to choose another strobe or beacon mode. If it's implemented the same way in MODES, again, I can't think of anything causing problems, in fact I think it's an improvement all around:

if in MODES, locked in at mode #1 (lowest):

• one click: turns the light OFF
• press&hold: goes to last mode: max/turbo (currently it would turn the light OFF)

So clearly, it only has advantages to make this change... I'll put in on my list - should be in the next release.

Thanks joechina -- very good suggestion!