The max temperature around the side switch is ~45°C, which is fairly good. And after stepping down to the highest regulated brightness level, the max temperature is ~43°C after two hours.

Keep in mind that NarsilM is not designed to step down to the “highest regulated brightness level”. In ramping, the drops from max/turbo will be as follows:1st: 100% (150) to 55% (125)2nd: 55% (125) to 31% (105)3rd: 31% (105) to 14% (88)Drops will continue (if necessary), but stop occurring once it reaches about 150 lumens, or 0.35 amps.

So if it happens to stabilize within the upper part of the regulated mode, it is just a coincidence. Maybe a happy coincidence?

Highest fully regulated output would be the 7×7135 level, which should be somewhere around 500-600 lumens. However, you would have to switch to the mode groups from the ramping UI to reliably select that level.

It may be possible to get close in ramping if you use the switch blinks. I assume it still blinks twice when using the FET and once when using the regulated mode?

You would just ramp up to about 600 lm, release the switch and see if it blinks once or twice. If twice, then you need to ramp down a little. After a couple of tries, I can find that highest regulated level on my GT Mini.

Just FYI, the default mode set group (4) with (moon) – 0.25 – 3 – 33 – full FET have both the 1×7135 and 7×7135 selectable. They are the middle modes 3 and 33. Makes testing the runtimes and efficiency easier since theyre’s no way to activate those in ramping mode. No default 1×7135 like on the D4.

edit: this is from the Q8 quick manual. On the NarsilM reference manual the modes are called moon – 2 – 10 – 40 – full.

This light is using NarsilM v1.2, right? It has a reduced level at the top of the ramp and full turbo with a double click?

If so, then the mode sets are a bit different. Modes 1-6 use the top of the ramp as 100%. Modes 7-12 use full turbo as 100%.

This light is still new, so I’m not sure what exact UI it’s using or if it has any special tweaks.

It may be possible to get close in ramping if you use the switch blinks. I assume it still blinks twice when using the FET and once when using the regulated mode?

There’s a very subtle blip/pause at the 100% 7135 levels while ramping. So that helps too.

But I think there’s something wrong with the light not remembering the ramp/mode setting made in the config menu. Haven’t had to chance to test other options yet.

edit: it does remember the blinky modes on/off setting though so maybe the ramp/mode is a decision to prevent situation where the user accidentally deactivates ramping? At least it indicates that the non-volatile memory is working.

edit2: after another runtime test it did remember the mode config after several battery changes and didn’t revert to ramping

Is the ROT66’s code published anywhere? I’m not sure if I need to go bother someone about license compliance.

I sent Fireflies a message about it last month sometime, but I’ve been travelling and haven’t had time to follow up yet.

I’m sure he meant Narsil as the B and the N are right next to each other.

Fireflies contacted me about a week ago if it was okay for them to use the videos I made on NarsilM. I said sure and pointed them to Vestureofblood as he has a better video. That was the first time I had heard of this light.

If you look at their website here you can see where there say it’s using NarsilM version 1.2. I don’t know if it’s been tweaked or not to fit this light.

Well isn’t this the strangest thing. Now after doing another runtime test at 7×7135, it does remember the mode configuration. Before this I tried it at least 10 times and it always reverted back to ramping after power loss. Now it doesn’t do it after several battery swaps.

Well isn’t this the strangest thing. Now after doing another runtime test at 7×7135, it does remember the mode configuration. Before this I tried it at least 10 times and it always reverted back to ramping after power loss. Now it doesn’t do it after several battery swaps.

It’s probably missing a call to SaveConfig() somewhere, so it only saves sometimes. Or maybe there was weird stuff in ROM and it needed to wear-level over some bogus values. It’s hard to say. In either case, it sounds like there’s a bug somewhere.

If you look at their website here you can see where there say it’s using NarsilM version 1.2. I don’t know if it’s been tweaked or not to fit this light.

Thanks. I’ll try to follow up soon to clarify how the GPL works. Basically, it needs a conspicuous notice somewhere that it’s using free software, with a link to the code which shipped in the product. That’s usually the easiest method, anyway. If it’s modified from what is already published, things get a little more complicated… so I usually try to put an exact copy in the repo to make things easier.

Well isn’t this the strangest thing. Now after doing another runtime test at 7×7135, it does remember the mode configuration. Before this I tried it at least 10 times and it always reverted back to ramping after power loss. Now it doesn’t do it after several battery swaps.

It’s probably missing a call to SaveConfig() somewhere, so it only saves sometimes. Or maybe there was weird stuff in ROM and it needed to wear-level over some bogus values. It’s hard to say. In either case, it sounds like there’s a bug somewhere.

Is this something that can be rectified on lights that were already sold or would that mean Fireflies needs to recompile everything and sell a new revision of their lights?

Hhmm. haven't heard of issues storing settings, but, anything is possible - there is wear leveling logic - think the "block" of settings is up to about 4 bytes now. I'm thinking it is saving, or attempting to save every time, just that something went wrong there with the addressing or something. Could be failing to load the setting,s then using defaults when this problem occurs.

Well isn’t this the strangest thing. Now after doing another runtime test at 7×7135, it does remember the mode configuration. Before this I tried it at least 10 times and it always reverted back to ramping after power loss. Now it doesn’t do it after several battery swaps.

seems a bit strange, we tried 11pcs ROT66 randomly today , all can remember Mode group without problem.

Good that it isn't widespread. Let's hope it doesn't randomly appear on lights. Just something that everyone should try out though.

Been think'n bout it more - might have seen this... pm sent to Fireflies and TK. I guess the Q8 is the largest deployment of NarsilM and don't think I've heard of it happening with the Q8, though that was an earlier version. Dunno if I only saw it while in development/debug or what...

Well isn’t this the strangest thing. Now after doing another runtime test at 7×7135, it does remember the mode configuration. Before this I tried it at least 10 times and it always reverted back to ramping after power loss. Now it doesn’t do it after several battery swaps.

It’s probably missing a call to SaveConfig() somewhere, so it only saves sometimes. Or maybe there was weird stuff in ROM and it needed to wear-level over some bogus values. It’s hard to say. In either case, it sounds like there’s a bug somewhere.

Is this something that can be rectified on lights that were already sold or would that mean Fireflies needs to recompile everything and sell a new revision of their lights?

The max temperature around the side switch is ~45°C, which is fairly good. And after stepping down to the highest regulated brightness level, the max temperature is ~43°C after two hours.

Keep in mind that NarsilM is not designed to step down to the “highest regulated brightness level”. In ramping, the drops from max/turbo will be as follows:
1st: 100% (150) to 55% (125)
2nd: 55% (125) to 31% (105)
3rd: 31% (105) to 14% (88)
Drops will continue (if necessary), but stop occurring once it reaches about 150 lumens, or 0.35 amps.

So if it happens to stabilize within the upper part of the regulated mode, it is just a coincidence. Maybe a happy coincidence?

Well, I did trace NasilM to find out its step-down logic before, but… I tend to let the runtime curves speak for me this time

4 hours at 700 lumens of 219B 9080 makes this an extremely practical light. When did you guys order? Howcome you got it so fast? I ordered mine on the first or second day it was announced but tracking status says “2018-08-10 06:02 – Origin Post is Preparing Shipment, We have received notice that the originating post is preparing to dispatch this mail piece”

Also Fireflies does not respond to my multiple emails. How did you guys get a hold of him?

I’m curious how long it takes to heat up if you disable the thermal stepdown. I don’t really like the behaviour with the Q8 because it never steps back up, so I just have it disabled and can generally get pretty decent usage out of turbo before it gets too hot to hold (i.e. high 50s C). Certainly more than 24 seconds.