NarsilM - configurable e-switch firmware for Multi channels, new v1.2 BETA

504 posts / 0 new
Last post
emarkd
emarkd's picture
Offline
Last seen: 9 months 4 days ago
Joined: 04/14/2015 - 22:04
Posts: 1608
Location: Georgia, USA
ToyKeeper wrote:
emarkd wrote:
Here’s what I want — when I hit that mechanical switch I want it to come on in turbo (like it already does), but if I’m holding down the e-switch I want it to come on in moonlight. (Yes I stole that idea from EagleTac). Looking at the code I thought that would be easy. I tried adding a simple if(isPressed()) check to the STARTUP_LIGHT_OFF codeblock just inside the main method, but that didn’t work for some reason.

I’m not sure why it didn’t work for you. It worked for me:

https://pastebin.ca/3870461

However, there is one caveat. For some reason, after booting in moon mode, it refuses to ramp until after turning the light off and back on. Instead of holding to ramp, it needs a “click, release, hold” to ramp the first time. No idea why, and I didn’t see an obvious fix. It still responds for other hold events though, like entering config mode or triggering the auto-lockout after 20 seconds. But I think maybe the “holdHandled” var is getting stuck in the wrong state somehow until after a regular click.

Thanks TK, I’ll give your code a try. On first glance I see the difference in what we did — I was putting my if-else statement inside the if(ramping) statement instead of outside and duplicating the check. Not sure what the difference is functionally since only one branch of that code is going to run anyway, but I guess there is one. I’ll pull up my edits and compare. Thank you!

emarkd
emarkd's picture
Offline
Last seen: 9 months 4 days ago
Joined: 04/14/2015 - 22:04
Posts: 1608
Location: Georgia, USA

Can confirm that code works on my setup too. Not sure what I was doing wrong, but thanks! I do have the same ‘bug’ you report, the ramping doesn’t work until the driver is cycled off and back on using the e-switch, and its got other flakiness like cycling off if you release the side switch too soon after power-up, but its a start. Thanks again!

steel_1024
steel_1024's picture
Offline
Last seen: 1 month 2 weeks ago
Joined: 10/17/2016 - 14:06
Posts: 488
Location: Taiwan

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)

Sorry for my poor english.

RotorHead64
RotorHead64's picture
Offline
Last seen: 10 months 2 weeks ago
Joined: 10/31/2015 - 02:49
Posts: 430
Location: United States

RotorHead64 wrote:

Tom E wrote:

Lexel wrote:
Tom E wrote:
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 yell

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

 

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
Offline
Last seen: 6 months 2 weeks ago
Joined: 10/23/2016 - 01:56
Posts: 42
Location: Minnesota, USA

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
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

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

The Emisar lamps have one.

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

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

Quote:

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
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

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 smile. 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 laughing.

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
MRsDNF's picture
Offline
Last seen: 1 month 1 week ago
Joined: 12/22/2011 - 21:18
Posts: 13473
Location: A light beam away from the missus in the land of Aus.

Thanks for the work Tom. Thumbs Up

 

djozz quotes, "it came with chinese lettering that is chinese to me".

                      "My man mousehole needs one too"

old4570 said "I'm not an expert , so don't suffer from any such technical restrictions".

Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.

 

vestureofblood
vestureofblood's picture
Offline
Last seen: 1 day 7 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

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?

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

Tom E
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

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
JasonWW's picture
Offline
Last seen: 18 min 3 sec ago
Joined: 10/22/2016 - 11:41
Posts: 12860
Location: Houston Texas

vestureofblood wrote:
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

Texas Ace Lumen Tube and JoshK Sphere calibrated with Maukka lights

Click this to go to signature links. I'm still around, just not reading many new threads.

vestureofblood
vestureofblood's picture
Offline
Last seen: 1 day 7 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

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 Smile

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 Smile

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

JasonWW
JasonWW's picture
Offline
Last seen: 18 min 3 sec ago
Joined: 10/22/2016 - 11:41
Posts: 12860
Location: Houston Texas

vestureofblood wrote:
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 Smile

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.

Texas Ace Lumen Tube and JoshK Sphere calibrated with Maukka lights

Click this to go to signature links. I'm still around, just not reading many new threads.

Tom E
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

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

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

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
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

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

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

vestureofblood wrote:

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
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

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
vestureofblood's picture
Offline
Last seen: 1 day 7 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

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?

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

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
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

joechina wrote:
"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!

 

Tom E
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

vestureofblood wrote:
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?

As joechina said, no. But this is easily modifiable in the source code - in "Setups.h":

// Custom define your blinky mode set here:
#define SPECIAL_MODES_SET  STROBE_MODE, POLICE_STROBE, BIKING_STROBE, BEACON_2S_MODE, BEACON_10S_MODE

Just change the order as you would like, or remove ones you don't want, to add ones. Right now, RANDOM_STROBE is not used but is available. Other special modes would have to be added though (software written).

JasonWW
JasonWW's picture
Offline
Last seen: 18 min 3 sec ago
Joined: 10/22/2016 - 11:41
Posts: 12860
Location: Houston Texas

joechina wrote:
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.

That sounds like a very nice refinement on the UI.

Texas Ace Lumen Tube and JoshK Sphere calibrated with Maukka lights

Click this to go to signature links. I'm still around, just not reading many new threads.

steel_1024
steel_1024's picture
Offline
Last seen: 1 month 2 weeks ago
Joined: 10/17/2016 - 14:06
Posts: 488
Location: Taiwan

Finally, I compiled a .hex file, NarsilM V1.0 3C1S
Did not change any CODE……

NarsilM.c
Channels.h
ModeSets.h
RampingTables.h
RegisterSettings.h

Setups-31S.h rename to Setups.h

tk-calibMTN17DDm.h
tk-calibWight.h
tk-delay.h
tk-random.h

I will flash to the ATtiny85 to test

Sorry for my poor english.

vestureofblood
vestureofblood's picture
Offline
Last seen: 1 day 7 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

Hi Tom,

Working on the UI vid today. Most everything seems to be going fine, but I have one hiccup. In the “modes” group the count seems to be off some how. On the ref sheet I see that the default when switched to modes should be group 4, but I get 5 mode as default. I tried switching to the first group and I got 2 mode, the second group I get 3 mode. I thought maybe the whole thing was just off by one click but group 5 for me is single mode.

I did try resetting to default, but the result is the same after ward. As far as I can tell everything else works as described in the sheet. I was able to change the moon mode levels etc. Any ideas?

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

giorgoskok
giorgoskok's picture
Offline
Last seen: 5 days 10 hours ago
Joined: 11/13/2015 - 10:46
Posts: 2671
Location: Greece

Matt , is moonlight mode enabled ?

If yes , modes are counted without the moonlight .

Tom E
Tom E's picture
Offline
Last seen: 6 hours 57 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

vestureofblood wrote:
Hi Tom, Working on the UI vid today. Most everything seems to be going fine, but I have one hiccup. In the "modes" group the count seems to be off some how. On the ref sheet I see that the default when switched to modes should be group 4, but I get 5 mode as default. I tried switching to the first group and I got 2 mode, the second group I get 3 mode. I thought maybe the whole thing was just off by one click but group 5 for me is single mode. I did try resetting to default, but the result is the same after ward. As far as I can tell everything else works as described in the sheet. I was able to change the moon mode levels etc. Any ideas?

Ohhh - think the mode sets are "unique" for the GT buck driver build.

I got all the info here. I'll post.

This is directly from the code:

//---------------------------------------------------------------------
//  Buck driver 2 channel modes
//---------------------------------------------------------------------

// 2.0 A max modes
// 1 mode                               2.0A
PROGMEM const byte modeFetSet1[] =  {   201};   // for analog control
PROGMEM const byte mode7135Set1[] = {   255};   // for LM3409 enable/PWM

// 2 modes /4                            25%   2.0A
PROGMEM const byte modeFetSet2[] =  {    42,   201};  // for analog control
PROGMEM const byte mode7135Set2[] = {   255,   255};  // for LM3409 enable/PWM

// 3 modes /3                         11%    33%   2.0A
PROGMEM const byte modeFetSet3[] =  {    26,    53,   201}; // for analog control
PROGMEM const byte mode7135Set3[] = {   255,   255,   255}; // for LM3409 enable/PWM

// 4 modes /2                        12.5%    25%    50%    2.0A
PROGMEM const byte modeFetSet4[] =  {    27,    42,    77,    201};  // for analog control
PROGMEM const byte mode7135Set4[] = {   255,   255,   255,    255};  // for LM3409 enable/PWM

// 5 modes cube-oot                       1%     7%    22%    52%   2.0A
PROGMEM const byte modeFetSet5[] =  {    25,    25,    39,    80,   201};  // for analog control
PROGMEM const byte mode7135Set5[] = {    24,   170,   255,   255,   255};  // for LM3409 enable/PWM

// 6 modes cube-root                      1%     5%    15%    32%    60%   2.0A
PROGMEM const byte modeFetSet6[] =  {    25,    25,    30,    51,    94,   201}; // for analog control
PROGMEM const byte mode7135Set6[] = {    24,   126,   255,   255,   255,   255}; // for LM3409 enable/PWM

// 2.5 A max modes
// 1 mode                               2.5A
PROGMEM const byte modeFetSet7[] =  {   255};   // for analog control
PROGMEM const byte mode7135Set7[] = {   255};   // for LM3409 enable/PWM

// 2 modes /4                            25%   2.5A
PROGMEM const byte modeFetSet8[] =  {    45,   255};  // for analog control
PROGMEM const byte mode7135Set8[] = {   255,   255};  // for LM3409 enable/PWM

// 3 modes /3                         11%    33%   2.5A
PROGMEM const byte modeFetSet9[] =  {    27,    58,   255}; // for analog control
PROGMEM const byte mode7135Set9[] = {   255,   255,   255}; // for LM3409 enable/PWM

// 4 modes /2                        12.5%    25%    50%    2.5A
PROGMEM const byte modeFetSet10[] =  {    29,    45,    86,    255}; // for analog control
PROGMEM const byte mode7135Set10[] = {   255,   255,   255,    255}; // for LM3409 enable/PWM

// 5 modes cube-oot                       1%     7%    22%    52%   2.5A
PROGMEM const byte modeFetSet11[] =  {    25,    25,    41,    90,   255}; // for analog control
PROGMEM const byte mode7135Set11[] = {    26,   185,   255,   255,   255}; // for LM3409 enable/PWM

// 6 modes cube-root                      1%     5%    15%    32%    60%   2.5A
PROGMEM const byte modeFetSet12[] =  {    25,    25,    31,    56,   106,   255};   // for analog control
PROGMEM const byte mode7135Set12[] = {    26,   136,   255,   255,   255,   255};   // for LM3409 enable/PWM

So what does all this mean?

First 6 sets max out at 2 amps, 2nd set of 6 are full power at 2.5A.

DEL's cube root is percentages calculated,similar to TK's python script that calculates lumens.

 

All these sets exclude moon mode. If you have moon mode enabled, then you'll get the modes above, but also starting with your currently set moon mode level.

 

Does this help? 

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

What Giorgoskok wrote.
If you choose only mode #1 and enable moonlight you end up with two modes.

If you choose mode set #7 (which has 7 values in the table) and enable moonlight you will end up with 8 brightness levels.

(On the Q8 product page is under product detail a table where it is clear that moonlight is included, when switched on https://www.banggood.com/BLF-Q8-4x-XP-L-5000LM-Professional-Multiple-Ope...LED-Flashlight-p-1194351.html )

Tom E
I guess the cube root modes are the evenly spread ones?

What is the reason for 2A instead of 2.5A max? Reduced wear?

MRsDNF
MRsDNF's picture
Offline
Last seen: 1 month 1 week ago
Joined: 12/22/2011 - 21:18
Posts: 13473
Location: A light beam away from the missus in the land of Aus.

joechina wrote:
What is the reason for 2A instead of 2.5A max? Reduced wear?

2A gives a longer in regulation run time while 2.5 amps is available with a double click. From memory the difference in output was somewhere around 13%.

 

djozz quotes, "it came with chinese lettering that is chinese to me".

                      "My man mousehole needs one too"

old4570 said "I'm not an expert , so don't suffer from any such technical restrictions".

Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.

 

Pages