Lumintop GT Mini (Thower) Beam shots and more!

[sbslider]

@JasonWW

@sbslider

How does the throw and such compare with a Thrunite TN4A? I know the TN4A is bigger/heavier, but I have it and wondering if the GT mini significantly out performs.

Which version, Xml2, xpl or xpl hi?

Xpl hi

[JasonWW]

@sbslider

@JasonWW

@sbslider

How does the throw and such compare with a Thrunite TN4A? I know the TN4A is bigger/heavier, but I have it and wondering if the GT mini significantly out performs.

Which version, Xml2, xpl or xpl hi?

Xpl hi

In that case the difference is not going to be huge. It’s hard to find specs for it but I did find some for a neutral white version with the xpl hi. Peak Beam Intensity: 52,340cd.
Max beam distance: 457m. It’s got a 46mm head compared to the GT Mini’s 50mm.

So the Mini still beats it. Plus the mini has a few more hundred lumens. I measured around 1200, but others have measured around 1400. My guess is that it’s not going to be as big a difference as with my C8, but still pretty noticeable.

[JasonWW]

@toobadorz

@JasonWW

UPDATE TO MANUAL

After trying mode 4 and mode 10 it appears that the groups are reversed.

Modes 1-6 use full turbo as 100% (5A)

Modes 7-12 use the top of the ramp as 100% (2.5A)

We definitely need an updated manual to reflect this.

Edit: And here it is.
GT Mini User Manaual
.

Thanks. And more to be corrected:

…If [temperature] is selected for auto step-down, the GTmini goes to 100% output. Leave the GT to heat to the desired limit, and then click to set that temperature as the trip point (the GTmini is huge, so this can take 20 minutes or longer, use fresh cells for this). Or click within 5 s to keep previous setting.

GTmini is not huge and it doesn’t take 20 mins to get hot. So this statement looks weird, probably caused by a simple replacement (GT to GTmini?)

The strobes are deactivated by default.

Strobes are all enabled by default, at least on my GTmini.

Yeah, it also says it takes 16 seconds to enter the menu, but it only seems to take about 8 Seconds.

Another error is where it says it requires button top cells. Since the GT mini has a spring on the driver it will work fine with flat top as well.

I notice it says it’s using NarsilM v1.3 instead of v1.2. All previous reports showed it was using v1.2.

[sbslider]

Thanks for the comparison, I appreciate it.

[sbslider]

@JasonWW

@toobadorz

@JasonWW

UPDATE TO MANUAL

After trying mode 4 and mode 10 it appears that the groups are reversed.

Modes 1-6 use full turbo as 100% (5A)

Modes 7-12 use the top of the ramp as 100% (2.5A)

We definitely need an updated manual to reflect this.

Edit: And here it is.
GT Mini User Manaual
.

Thanks. And more to be corrected:

…If [temperature] is selected for auto step-down, the GTmini goes to 100% output. Leave the GT to heat to the desired limit, and then click to set that temperature as the trip point (the GTmini is huge, so this can take 20 minutes or longer, use fresh cells for this). Or click within 5 s to keep previous setting.

GTmini is not huge and it doesn’t take 20 mins to get hot. So this statement looks weird, probably caused by a simple replacement (GT to GTmini?)

The strobes are deactivated by default.

Strobes are all enabled by default, at least on my GTmini.

Yeah, it also says it takes 16 seconds to enter the menu, but it only seems to take about 8 Seconds.

Another error is where it says it requires button top cells. Since the GT mini has a spring on the driver it will work fine with flat top as well.

I notice it says it’s using NarsilM v1.3 instead of v1.2. All previous reports showed it was using v1.2.

Thanks for the clarification about the cells, that was a reason imo for looking elsewhere. Not a huge deal, but I prefer flat top cells in general, and think double springs are a plus also.

[Tom_E]

The Mini does use V1.3 by virtue of it blinking out 1.3. Not sure where it came from, guessing TA. Dunno, maybe I provided it wayyy back?

[toobadorz]

@JasonWW

Yeah, it also says it takes 16 seconds to enter the menu, but it only seems to take about 8 Seconds.

Another error is where it says it requires button top cells. Since the GT mini has a spring on the driver it will work fine with flat top as well.

I notice it says it’s using NarsilM v1.3 instead of v1.2. All previous reports showed it was using v1.2.

Nice catch!

[joechina]

Tom
Texas Ace used a NarsilM 1.3 Beta
I think you did provide it.
Maybe to Dell?

[Tom_E]

@joechina

Tom Texas Ace used a NarsilM 1.3 Beta I think you did provide it. Maybe to Dell?

Ok, probably posted the v1.3 BETA for him to use on Nov 16th, then on Jan 28th posted a v1.3 with the "new" S42 support, but nothing seemed to come out of that, least not so far.

[joechina]

Tom E
you have a PM

[Texas_Ace]

@JasonWW

Yeah, it also says it takes 16 seconds to enter the menu, but it only seems to take about 8 Seconds.

Another error is where it says it requires button top cells. Since the GT mini has a spring on the driver it will work fine with flat top as well.

I notice it says it’s using NarsilM v1.3 instead of v1.2. All previous reports showed it was using v1.2.

Ok, these issues I think are explained by them using a different firmware revision then I planned on. The final firmware I sent them should be as the manual states but I sent then an earlier version that is closer to what it sounds like ya’ll are seeing. They were supposed to of used the latest version but it looks like it didn’t make it into production.

IIRC these are about the limit of the changes + some minor changes to the ramp / mode spacing between the revisions.

[Texas_Ace]

@Tom E

The Mini does use V1.3 by virtue of it blinking out 1.3. Not sure where it came from, guessing TA. Dunno, maybe I provided it wayyy back?

Yes, it was from me, although it looks like they used the prototype firmware I made for testing it instead of the final firmware with the refined ramp / mode groups and other settings. Not a big deal but the things mentioned above are a little different.

[mulletbay1]

Hi, I hv a mod Acebeam l16, love it. How does the lumintop gt mini’s beam patter n throw compare?

[d_t_a]

@Texas_Ace

@Tom E

The Mini does use V1.3 by virtue of it blinking out 1.3. Not sure where it came from, guessing TA. Dunno, maybe I provided it wayyy back?

Yes, it was from me, although it looks like they used the prototype firmware I made for testing it instead of the final firmware with the refined ramp / mode groups and other settings. Not a big deal but the things mentioned above are a little different.

Would it be alright to ask, what are the differences between the "proposed" final firmware you intended, compared to what is actually installed on the GT Mini?

Sharing a video beamshot of the GT Mini neutral-white:

(building on the other side is about 160 meters or 400 feet away from the flashlight)

Lumintop GT Mini (XPL-Hi NW, 1200 lumens, ~750 meters throw) beamshot

compare to an Astrolux C8 (XPL-Hi 3A NW, 1300 lumens)
www.youtube.com/embed/roxXelnRQwo

[Texas_Ace]

@d_t_a

@Texas_Ace

@Tom E

The Mini does use V1.3 by virtue of it blinking out 1.3. Not sure where it came from, guessing TA. Dunno, maybe I provided it wayyy back?

Yes, it was from me, although it looks like they used the prototype firmware I made for testing it instead of the final firmware with the refined ramp / mode groups and other settings. Not a big deal but the things mentioned above are a little different.

Would it be OK to ask, what are the differences between the “proposed” final firmware you intended, compared to what is actually installed on the GT Mini?

Basically what I said in the quote, I don’t remember all the changes but the biggest change was an improved ramp that was smoother, better mode groups and a few minor tweaks to some other settings that were really just from my drive for the best I can do.

A few of those changes were noted earlier, the menu timing was extended to 16 seconds instead of 8 seconds ect.

Overall most will not notice the difference, the base firmware I used was basically the GT firmware so it still works fine, it was just not optimized for this driver and light.

[toobadorz]

@Texas_Ace

Overall most will not notice the difference, the base firmware I used was basically the GT firmware so it still works fine, it was just not optimized for this driver and light.

Yeah. So far the most noticeable part is, when stepping down from FET to 7135 due to low battery, the light is actually becoming brighter. This is because the firmware avoids activating two channels at once, and when the battery voltage is low, the FET can be darker than the 7135, thus “stepping-down to a brighter level” can happen. This can certainly be fixed by tuning the voltage that triggers this.

[Texas_Ace]

@toobadorz

@Texas_Ace

Overall most will not notice the difference, the base firmware I used was basically the GT firmware so it still works fine, it was just not optimized for this driver and light.

Yeah. So far the most noticeable part is, when stepping down from FET to 7135 due to low battery, the light is actually becoming brighter. This is because the firmware avoids activating two channels at once, and when the battery voltage is low, the FET can be darker than the 7135, thus “stepping-down to a brighter level” can happen. This can certainly be fixed by tuning the voltage that triggers this.

Yes, that is a possible issue with how it is setup now. A minor but notable issues.

This firmware was just meant for prototyping, it was never intended to be used in the final driver.

[Niko]

i have booth, gt is slighty longer but better lies in hand. emisar is more powerfull. booth are great

[Newlumen]

[quote=Niko]
i have booth, gt is slighty longer but better lies in hand. emisar is more powerfull. booth are great

you might be right about the d1s. I dont have a mini gt or calibrated lights for the tube… i measured d1s cool white @ 1400 lumen using Sony vtc6…

[mortuus]

emisar is not more powerful, i think the beam on gt mini is slightly sharper.