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?
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.
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%.
Previous post has the GT mode sets. The Q8 is different.
As the Mrs said (Steve), the intent is prolonged runtime to max at 2.0A. If you want the full 2.5A, there's a duplicate set of modes available shown above, plus in ramping, ramping max's out at 2.0A but a 2X click goes to turbo at 2.5A.
joechina, According to your cheat sheet it is 4 clicks for lockout in both ramping and discrete mode, I just verified with one of mine as well.
[edit]It does work this way, but I read the UI cheat sheet wrong. Tom has verified this is a bug.[/edit]
2 quick clicks followed by click&hold works for me (as designed)
4X clicks though will restore it from lockout, as well as 2X clicks + click&hold (as designed, both ways work).
Just tried it: the 4X clicks to enter lockout in MODES is also working -- this was unintended. I did not want it to function like this because someone can click quickly through modes and unintentionally lockout the light. Granted though, I made the multi click operations pretty quick, so it's harder to get it occur unintentionally, but it can happen.
Ok, another bug
fyi: Don't have a Q8 with me, but I'm using a Manker U11 modded with NarsilM v1.0, so exactly the same as the Q8, or should be?
Hey, you put a lot of work into that sheet, and it has helped me figure out how to use this great light. But, apparently, I need to print it even BIGGER, because I neglected to read that the left two tables differ based on “from on” or “from off” and have left/right sections for ramping or modes.
Your printer should have a poster mode. Print it in double size and glue it together.
Another way to use:
- put the PDF on your smartphone. There you can zoom in.
view the PDF on your computer screen.
Yes the left part has the clicks for
- Lamp is OFF for RAMPING
- Lamp is ON for RAMPING
- Lamp is OFF for MODES
Lamp is ON for MODES
Each row has the same klicks, it is sorted by clicks, not by actions: You see there is double click for RAMPING, but not for MODES. And if you want battery check when you are in MODES you can see you reach it only if the lamp is off.
Let me start by saying thanks so much to you all for helping me.
.
Thank you, I will be sure to incorporate these points.
Yes, that is definitely part of the problem I had. Didn’t realize that.
YES! That definitely looks like what I am seeing. Will you be making a ref sheet with this outlined in it? I want to direct people to the sheets you an JoeChina have made right form the start.
Sometimes I think the complications and issues associated with the indicator light in the side switch are just not worth it. I’m mainly referring to mass production lights like the Q8.
Would it be a step backwards or an improvement to just have the side switch light stay on whenever the batteries are connected?
I’ve got two narsil lights that I’ve wired up so the switch always stays lit and it’s been super simple. No funny blinks, you always know when power is applied or if the light is locked.
Since Narsil can be quite complex, why make it even more complex with indicator functionality?
Well it's open source. It's easy to add a simple compile switch to just turn it on upon power up and stay on. I could also add this to the switch configuration settings UI. You lose some functionality of course - channel use indicator blinks, LVP blinks, etc.