First you go into the setup menu and switch from ramping to mode sets. Exit menu and confirm change.
Then you go back into the menu and change the number of levels to 8.
Do you need instructions on this?
I come to 2 blinks and then 8 but don’t know how to confirm that, it won’t memorise…
Who & what is this referring to??
If you are still in ramping, you look for 2 fast blinks then one slow blink, click once and confirm the light blinks when you press the button. Then let it finish.
Now you should be out of ramping mode and into mode sets. Now you go back into the menu and wait for 2 fast and 2 slow. Now you have to click 8 times. Again, make sure each button click gives a blink of light. Then let it finish the menu.
Now you should be set.
Here is my video showing how the menu system works.
Refer to the GT Mini menu for its options. I use the Q8 menu in the video.
Mine sometimes don’t respond to the switch. Is that the switch problem you are talking about?
Seams like it does it a lot in the configure menu. And when going from turbo to lower level, sometimes it just turns off like its not counting the 2 clicks.
It always turns off from Turbo to a lower level. That’s how the UI works.
I’m not sure who you are asking about the switch. Some peoples light had a switch that didn’t always make contact.
I have had lights with perfect switches sometimes act like it doesn’t make contact when I’m in the menu setup. This is why it’s important to look for the confirmation blink. Sometimes I may have to click four times just to get the two blinks that I want. I don’t know why it does that. Luckily I pretty much never have to change anything in the menu once I get it set up the first time.
If I run mine up to a mid level and double click it goes to Turbo, and if I double click from Turbo (blinkys disabled) it returns to the mid level.
Sometimes it just turns off with the double click from Turbo.
Edit- this only happens when I am at the top of the ramp.
Thank you very much. The main problem was that I didn’t know that first 2 blinks didn’t count.
I managed to get into Mode set no. that I want and to enable mode memory, and want to know more about this 100% power modes that are used in Mode set no. do they use FET on all 100% power modes, I choose mode set 8 so I’m little confused with pictures in your videos, so don’t know it is using FET ?
That’s why I said don’t use the pictures in my video. You need to use the manual for the GT Mini.
Yes, at 100% it is using the FET. I think this is a 2 channel driver with only one 7135, so anything above about 200 lumen should be from the FET. Maybe someone can confirm that.
My manual says mode sets
1-6 100% = 2.3 A LED drive
7-12 100% = 4.5 A LED drive
I am assuming they are using 6 7135 chips and a fet.
Driver: 17W, 4.5 A FET driver etc etc
Been playing with mine some more tonight.
I only get double click error from Turbo if I am at the top of the ramp.
Edit. Guessing the jump from 2.3 to 4.5 and back.
I think your looking at an incorrect manual.
Go to this thread and you will see a link for the manual. I’ll add the manual link here as well.
If you look at the back of the driver there are no 7135 chips. So it can’t have 6 chips. There is no room for them on the other side.
What type of error do you mean? The brightness should go up a little more when you go from top of ramp to turbo.
Ok. They sent me uncorrect manual.
All the printed manuals are incorrect. Was this not mentioned in this thread? We had a discussion about it in the other thread I linked to.
Gt mini is a FET+1.
Just to have the info posted heres the BOM (I cloned the GT mini driver when making my FET+1 drivers)
R1 FET Pull-down: 100k <1%
R2 Gate resistor : 47ohm
R3 input filter : 4.7ohm
R4 voltage divider high side : 910k
R5 voltage divider low side : 300k
R6 AUX LED: 10K <1%
C1 10uF X5R or X7R
C1 0.1uF
FET LFPAK56 (SO8 also fits same pad)
Thanks, thats what I was thinking. So any brightness level above the 7135’s 0.35A current (about 200 lumen) will be going through the FET.
Sorta. ToyKeeper has explained it all in intricate detail before but the FET kicks in with PWM over the ceiling of the 7135… the 7135 keeps putting out 100% along with the increasing level of the FET right up until level 7, where the 7135 is cut off and it’s 100% FET.
Not so easy to say how many lumens the 350mA of the 7135 chip produces as that number will be dependent on the emitter used, cell used, efficiency of the circuit, a number of things.
Edit: Mine (GT Mini) has a Samsung LH351D 80 CRI 5000K emitter and makes 168 lumens at the 7135 chip ceiling , from an LG HG6 20650 cell well rested.
EditII: Another light using an XP-L HI from a 26650 makes 164 lumens, also well rested using a LiitoKala Black.
EditIII: My little TK05 using a 14500 cell and the 80 CRI Samsung makes 156 lumens at the top of the 7135 chip.
EditIV: On an extreme end, my 458 Ham’r is making 862 lumens at the top of the 7135 chip output.
While we are talking about a single emitter here, my Quad D1S makes 531 on the ceiling of the 7135 chip. So there are indeed variables…
Thanks CK and DB for clearing that up.
Thanks JasonWW for reading every post in this thread and setting me str8 on the misprinted manual. I only recently received this light I have not had a chance to dismantle it.
I do like the light but the error/glitch in the UI is annoying.
I see what you mean. The fact of the matter is that a dbl clk is not designed to return to the previous level. I think it’s just a glitch that it does (assuming you have blinkies disabled and are below the ramp top).
The solution is to just slow down your button presses. Don’t try to dbl click. Just let the light turn off and back on. This is how all my other Narsil based lights works.
Or, if you like that ability, don’t run it at the top of the ramp. Run it just below the top.
Yep, all my other Narsil based lights have this glitch also
Edit- Now I know its not a switch problem.
Thanks