Fireflies ROT66 review (3x18650, 9x219B)

The default mode-set (4) already has all of them. i.e., Moonlight (if enabled) - 1x7135 (10) - 1x7135 (100) - 7x7135 (100) - FET (100).

Thanks! Will try them out. The manual indicates mode-set (4) as 0.25 - 3 - 33 - full , with description “3%=max 7135” and “33%=mixed”, so it got me stumped…

So going by the above, any mode-sets in the manual’s description that has “3” and “33” will be 1x7135(100) and 7x7135(100).

I suppose this also goes with the XPL-High version? In which case it is 14x7135(100) instead of 7x7135(100)?

Well, the manual simply copies the Q8 cheat sheet and thus is not 100% correct, at least the mode-sets described are really meaningless. ROT66 utilizes 3 channels, and in this case NarsilM features only 8 mode-sets (not 12). And these 8 mode-sets are slightly adjusted for this light so they are actually different from the original, meaning that you still won’t know the exact mode-set configurations even though the NarsilM is open source. Fireflies really should correct the manual.

For the default mode-set (4), exactly.

Thanks for the info, toobadorz.

Where can we get more info about each of the 8 mode sets for the Modes Group? (or if someone has more info about them…)

Maybe Freeme can ask for it? He's in contact with them anyway due to the worrying findings Vinh has reported on his two ROT66.

https://www.candlepowerforums.com/vb/showthread.php?450353-FireFlies-ROT66vn-Most-Compact-PopCan

Hm if the alignment with the optic is that tight I guess I see why they didnt go with 219C/LH351D/XPL HD/2

Based on the information from Lexel, I did create a table for the mode-sets. This shall be correct if they don’t change the definition again.

Somehow Vinh managed to fit the LH351Ds in the light.

Now we just need to convert that table into the normal percentages.

The real percentages are a bit pointless, because they can vary greatly from LED to LED (219B, XP-L HI, …) and from light to light. This is because the 100% output of the light is purely driven by FET, and that number is not stable at all.

How is the average person going to relate? Most folks are not going to understand your chart. That’s all I’m saying.

The best way is simply measure the lumen numbers of each mode in each mode-set and then create separate tables, for each LED versions. This is what should be done by the manufacturer.

Thanks a lot! Nice to see that every mode set actually has the 7135 100% modes included. Also quite interesting that one of them (#3) only has the 6x7135 while all the other are 7x7135. Also the mode set #7 level 6. Are you sure it’s 0|100|39.2 and not 100|100|39.2?

Exactly. The definition from Lexel:

// 3 modes (7135-7135s-max) ~10% ~50% max
PROGMEM const byte mode7135Set3 = { 255, 0, 0};
PROGMEM const byte mode7135sSet3 ={ 0, 255, 0};
PROGMEM const byte modeFetSet3 = { 0, 0, 255};

// 7 modes (0.5-2.5-5-10-25-50-max) ~0.4% ~2% ~8% ~20% ~50% ~80% max
PROGMEM const byte mode7135Set7 = { 8, 200, 255, 255, 255, 0, 0};
PROGMEM const byte mode7135sSet7 ={ 0, 0, 40, 120, 255, 255, 0};
PROGMEM const byte modeFetSet7 = { 0, 0, 0, 0, 0, 100, 255};

Here you can find all of them.

Well can’t argue with the source, thanks!

Nice table.

So it’s possible to also get No PWM from 7135x6 (100%).

I would presume the 7135x6(100) will also have a nice output, just a tad lower than the 7135x7(100).

If one wants to cycle through all NoPWM modes, then that would have to be 7135x1(100) - 7135x6(100) - 7135x7(100) - FET (100%), although the visible difference between 7135x6(100) and 7135x7(100%) might not be that noticeable.

Mode-set #7 has the most (7) brightness levels — is this supposed to match the “BLF A6” 7-evenly-spaced-brightness-levels ?

I converted toobadorz table into the following (actually, the following I did may not necessarily be more easy to read…)
Mode-set

  1. : FET (100%)
  2. : 7135x1 (100) - FET (100)
  3. : 7135x1 (100) - 7135x6 (100) - FET (100%)
  4. : 7135x1 (9.8) - 7135x1 (100) - 7135x7 (100) - FET (100)
  5. : 7135x1 (9.8) - 7135x1 (39.2) - 7135x7 (100) - FET (100)
  6. : 7135x1 (6.7) - 7135x1 (31.4) - 7135x1 (100) - [7135x1(100)+7135x6(39.2)] - 7135x7 (100) - FET (100%)
  7. : 7135x1 (3.1) - 7135x1 (78.4) - [7135x1(100)+7135x6(15.7)] - [7135x1(100)+7135x6(47.1)] - 7135x7 (100) - [7135x6(100)+FET (39.2%)] - FET (100%)
  8. : 7135x7 (100) - FET (100)

No “muggle mode” mode-set? (eg. where the max level is say 7135x6(100) or 7135x7(100) :wink:

That 7135x6 (100) mode is ~600 lumens. It may be useful when you feel the light can be too hot to be held at 7135x7 (100) :wink:

And, one important thing to be aware of: though only 8 mode-sets are available, the firmware still accepts an input value between 9~12. But if you give this the result can be unpredictable, since this can trigger a memory read from an unknown block.

Has anybody a Maukka calibrated lumintube. and Hi Version of the ROT66?

And can you measure Modeset 3?
It’s (moon) — max7135 — max7135s — FET

And which LEDs you have:
XPL Hi V3 1A Cool White
XPL Hi V3 3A 5000K Neutral White
XPL HI U6 5B 4000K

Thank you

This request will like take a while to compile… I suppose no one tried ordering all the different configurations of the ROT66, but it would be nice to also see the beamshots (and tint differences) of the ROT66 219B and those 3 different XPL-Hi tints…

Even if someone has all those ROT66 variants, the lumen numbers measured may still be a bit far from the one you really get. I’m saying so because on my XP-L HI 3A V3 ROT66, the LEDs are also crushed like Vinh described at CPF . And after removing some of the obvious white fragments on the LED the numbers I got were indeed improved.

So don’t expect you can get one with similar lumen numbers as reported by other people.