Fireflies ROT66 Flashlight

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.

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.

No, not unless Fireflies rewrote the NarsilM code, which seems unlikely. It seems they did.

Modes 4 and 10 (each have 4 brightness levels, not counting moonlight) are spaced as follows:

12.5%
25%
50%
100%

This is based on the percentage of light.

If moonlight is turned on, you will see 5 total levels.

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

FireFlies, could you please explain the light not retaining settings between cell switches?

Oh how I crave beam shots!

Comparison with the Q8 from steel_1024:

Barsil?

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.

Those beamshot comparisons sure doesn’t look like 10k lumens. It looks less output than the q8.
I ordered a r0t66 anyways hehe

That’s because it’s the 5000 lumen 219B version.

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.

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.

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.

I really wonder who is behind Fireflies - suppose Lexel knows because he had to be dealing with someone there. This is a one product company, they could be gone tomorrow. There sure ain't much info on their website. They want dealers but provide no info on who they are: http://www.ff-light.com/index.php?route=information/information&information_id=7

I agree with TK - I'd like to see a link to the source code since they are claiming NarsilM v1.2. There are tons of compile options in V1.2, so all depends on the exact v1.2 source code configuration.

Oh boy, might have to buy one or two of these just to see what's going on... Been debating spending the money. This is pretty weird.

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