Just FYI, the default mode set group (4) with (moon) - 0.25 - 3 - 33 - full FET have both the 1x7135 and 7x7135 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 1x7135 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.
And with a quick testing without proper sphere calibration and just using a lux meter I measured the 7x7135 mode at about 720 lumens and the 1x7135 at 105 lumens.
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? :partying_face:
It definitely should not do that. All settings (modes, thermal, etc…) should be stored permanently unless you go into the menu and change them. This will need investigating.
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.
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
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 7x7135, 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.