Fireflies ROT66 Flashlight

[Lexel]

OUT_CHANNELS == 3 // Triple Channel
//———————————————————————————————————————————-

//—————————- MODE SETS (must be low to high) —————————————

// 1 mode (max) max
PROGMEM const byte mode7135Set1[] = { 0}; // for single 7135
PROGMEM const byte mode7135sSet1[] ={ 0}; // for 7135 bank
PROGMEM const byte modeFetSet1[] = { 255}; // FET only

// 2 modes (7135-FET) ~10% max
PROGMEM const byte mode7135Set2[] = { 255, 0};
PROGMEM const byte mode7135sSet2[] ={ 0, 0};
PROGMEM const byte modeFetSet2[] = { 0, 255};

// 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};

// 4 modes (1.2-10-50-max) ~1.2% ~10% ~60% max
PROGMEM const byte mode7135Set4[] = { 25, 255, 255, 0};
PROGMEM const byte mode7135sSet4[] ={ 0, 0, 255, 0};
PROGMEM const byte modeFetSet4[] = { 0, 0, 0, 255};

// 5 modes (1.2-5-10-50-max) ~1.2% ~4,5% ~10% ~60% max
PROGMEM const byte mode7135Set5[] = { 25, 100, 255, 255, 0};
PROGMEM const byte mode7135sSet5[] ={ 0, 0, 0, 255, 0};
PROGMEM const byte modeFetSet5[] = { 0, 0, 0, 0, 255};

// 6 modes 0.8-2-5-10-50-max ~0.8% ~2% ~5% ~10% ~60% max
PROGMEM const byte mode7135Set6[] = { 17, 80, 255, 255, 255, 0};
PROGMEM const byte mode7135sSet6[] ={ 0, 0, 0, 100, 255, 0};
PROGMEM const byte modeFetSet6[] = { 0, 0, 0, 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};

// 2 modes (all 7135s-FET) ~60% max
PROGMEM const byte mode7135Set8[] = { 255, 0};
PROGMEM const byte mode7135sSet8[] ={ 255, 0};
PROGMEM const byte modeFetSet8[] = { 0, 255};

[Bob_McBob]

@toobadorz

(The first 5 minutes)

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.

[toobadorz]

@Lexel

OUT_CHANNELS == 3 // Triple Channel
//———————————————————————————————————————————-

//—————————- MODE SETS (must be low to high) —————————————

// 1 mode (max) max
PROGMEM const byte mode7135Set1 = { 0}; // for single 7135
PROGMEM const byte mode7135sSet1 ={ 0}; // for 7135 bank
PROGMEM const byte modeFetSet1 = { 255}; // FET only

// 2 modes (7135-FET) ~10% max
PROGMEM const byte mode7135Set2 = { 255, 0};
PROGMEM const byte mode7135sSet2 ={ 0, 0};
PROGMEM const byte modeFetSet2 = { 0, 255};

// 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};

// 4 modes (1.2-10-50-max) ~1.2% ~10% ~60% max
PROGMEM const byte mode7135Set4 = { 25, 255, 255, 0};
PROGMEM const byte mode7135sSet4 ={ 0, 0, 255, 0};
PROGMEM const byte modeFetSet4 = { 0, 0, 0, 255};

// 5 modes (1.2-5-10-50-max) ~1.2% ~4,5% ~10% ~60% max
PROGMEM const byte mode7135Set5 = { 25, 100, 255, 255, 0};
PROGMEM const byte mode7135sSet5 ={ 0, 0, 0, 255, 0};
PROGMEM const byte modeFetSet5 = { 0, 0, 0, 0, 255};

// 6 modes 0.8-2-5-10-50-max ~0.8% ~2% ~5% ~10% ~60% max
PROGMEM const byte mode7135Set6 = { 17, 80, 255, 255, 255, 0};
PROGMEM const byte mode7135sSet6 ={ 0, 0, 0, 100, 255, 0};
PROGMEM const byte modeFetSet6 = { 0, 0, 0, 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};

// 2 modes (all 7135s-FET) ~60% max
PROGMEM const byte mode7135Set8 = { 255, 0};
PROGMEM const byte mode7135sSet8 ={ 255, 0};
PROGMEM const byte modeFetSet8 = { 0, 255};

Good! This is taken from the last version used in ROT66, right? The mode configurations appear slightly adjusted. Will this modified NarsilM become available for download?

[ToyKeeper]

@Tom E

Oh boy, might have to buy one or two of these just to see what’s going on… Been debating spending the money.

If anyone should receive one for free, it’s you.

Mostly I just want to make sure people understand and follow the license, which requires publishing the code used in the product. I wouldn’t complain about a free light, and if I had one I’d probably port other code to run on it, but my main concern is that everything stays open.

[toobadorz]

@Bob_McBob

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.

ROT66 heated up really quickly. If you don’t like the default thermal step-down, you may set it to a higher value, or pick one of those NarsilM pre-defined step-down timers (60secs, 90secs, 2 mins, 3 mins, 5 mins, 7 mins). But do not disable it completely. I once tried to disable the step-down and cooled the light with two fans. However the surface temperature still went up and up, to 108°C, when Turbo was on. That’s dangerous…

[ToyKeeper]

@Tom E

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 don’t know what the issue is. Emisar had kind of a similar issue though, and I think this is the revision which fixed it in RampingIOS:

https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/revision/186.1.11

[ToyKeeper]

@FireFlies

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

If I understand correctly, it only forgets when the batteries are removed… and it doesn’t always happen.

[charles_lin]

Received my Fireflies yesterday!

Nichia 219B SW45K R0908 vs. XPL HI 5000K 3A

Size comparison

Beamshots (Camera in Manual Setting, WB set 5000k)








GIF

[shirnask]

Very nice, Thanks

[Tom_E]

@ToyKeeper

@Tom E

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 don’t know what the issue is. Emisar had kind of a similar issue though, and I think this is the revision which fixed it in RampingIOS: https://bazaar.launchpad.net/~toykeeper/flashlight-firmw

Toare/trunk/revision/186.1.11

Ohh, thanx! I'll check it out.

[Bob_McBob]

@charles lin

Size comparison

The size comparison is really useful. Definitely a bit more pocketable than the Q8, though I can see why it heats up faster on turbo. I’m always surprised by how chunky the M43 is.

[SKV89]

Thanks Charles Lin! You post some of the best comparisons I’ve seen! I’m surprised the MF01 looks so much brighter than the Fireflies XPL-HI version. The MF01 219C makes about 7k real lumens. Whereas the XP-L hi ROT66 is supposed to make 10k lumens. Do you have a TA lumen sphere to compare the two?

[Jay]

Thanks for the pics Charles, very helpful. Noticed you have the MF01 beamshot in the gif but not standalone. Any chance you could edit that one in there?

[contactcr]

@SKV89

Thanks Charles Lin! You post some of the best comparisons I’ve seen! I’m surprised the MF01 looks so much brighter than the Fireflies XPL-HI version. The MF01 219C makes about 7k real lumens. Whereas the XP-L hi ROT66 is supposed to make 10k lumens. Do you have a TA lumen sphere to compare the two?

It does look quite bright but honestly the floody LEDs really show off at this short distance. 7k vs 10k lumens is not much difference really and especially since the HI is more focused it’s probably just the extra 3k all in the middle where it’s already too bright in the middle for the camera.

[Firelight2]

Awesome comparison Charles Lin!

So if you had to only choose one ROT66, would you go with the XPL HI or the Nichia?

[deleted-200707]

The Q8 is a wonderful light for the money and demonstrates its better reach in that picture quite well.

[iamlucky13]

@charles lin

Received my Fireflies yesterday!
Size comparison

Very nice! What do you think of the champagne color? I could see myself loving it or hating it, but can’t decide from the pictures.

[charles_lin]

@SKV89

Thanks Charles Lin! You post some of the best comparisons I’ve seen! I’m surprised the MF01 looks so much brighter than the Fireflies XPL-HI version. The MF01 219C makes about 7k real lumens. Whereas the XP-L hi ROT66 is supposed to make 10k lumens. Do you have a TA lumen sphere to compare the two?

My MF01 is running Lexel FET driver with NarsilM v1.2, it should output around 9000~10000 lm.
The best output munber I can get from ROT66 XP-L hi is 7480lm @ 0 second & 6650lm@30 seconds with VTC5A.

@Firelight2

Awesome comparison Charles Lin!

So if you had to only choose one ROT66, would you go with the XPL HI or the Nichia?

I personally prefer Nichia. very nice tint & it is only stock high output light use Nichia 219b R0908 as far I know. XPL HI runs very hot in turbo mode for only about 30~40 seconds.

@Jay

Thanks for the pics Charles, very helpful. Noticed you have the MF01 beamshot in the gif but not standalone. Any chance you could edit that one in there?

I’ll do it.

@iamlucky13

Very nice! What do you think of the champagne color? I could see myself loving it or hating it, but can’t decide from the pictures.

It is personal preference. I like the champagne color because it stand out against all the other dark color lights.

[SKV89]

@charles lin

My MF01 is running Lexel FET driver with NarsilM v1.2, it should output around 9000~10000 lm.
The best output munber I can get from ROT66 XP-L hi is 7480lm @ 0 second & 6650lm@30 seconds with VTC5A.

I’m surprised your MF01 look that much brighter than the ROT66 and even more surprised that it is so much more on the rosy side of the BBL than even the Cree 3A. I have two MF01, one stock and one with Lexel’s buck driver. The 219C tint on both is on the greenish side of the BBL. One is significantly greener than the other.

The MF01 renders colors the best in your comparison. I think you won the tint lottery with the 219C.

[JasonWW]

@toobadorz

@JasonWW

@toobadorz

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? :partying_face:

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

(Note: the peak brightness at 0s is higher with VTC6s)

(The first 5 minutes)

Does this concur with the the notes I quoted from the Q8 (FET+1)? I can’t really tell.

That first step down looks a bit larger than 100% to 55. Maybe more like 100 to 35%? Does that seem correct?