Doesn’t seem to want to budge.
I used a thin blade.
To wedge it out?
Sorted it 
Broke the clip on my KR4
Tried the modify the bends to make it closer to the body.
The clip was brittle, maybe work hardened from manufacturing.
Derp.
Perhaps can piggy back a clip on someones order….
Is it possible to buy 8pcs*3535 MCPCB?
I got my Blue Swirl D4V2 Ti and it is a very beautiful light!
Unfortunately, one of the switch LEDs is more than double as bright as the rest! This looks very bad in real life.
Hank, what can be done about this, please?
Unfortunately, this is something that we are not able to do anything about it.
The LEDs have different VF value, thus the brightness of the LEDs can not be the same, especially at low current. As you can see, even our advertising photo have different LED brightness.
Are they not the all the same type of LEDs? How do they have different VF?
Even the same type of LED from the same production can/will have different specs. That’s why they are binned, but usually not for these low cost LEDs.
Even the same type of LEDs, from the same reel, next to each can have different VF. The white LED tend to be more uniform, the warm LED has more chance to have different VF.
I see.
Thank you for the information.
phew glad I got white button LEDs then because that would really annoy me
I have 2 D4V2 Ti with cool white button LEDs and they are perfect.
I thought that with the warm emitters the warm button would look nice, and it does. But the brightness difference bugs me too. A pity it cannot be helped.
I have cool white switch LEDs, but one was significantly warmer than the rest. I turned the switch LEDs off in the code and reflashed. I found that I actually like it better without them on. The switch LEDs were very bright at night.
Edit: I’m pretty sure I just commented out “#define USE_BUTTON_LED” in cfg-emisar-d4v2.h.
Even on low mode they were too bright? I set mine hi or lo according to the light. My D4SV2 is bright on hi, but I like it that way around the house or on the nightstand.
How is the cfg file used? Flashed over the full firmware?
Not sure what you mean by that. It's a cfg file - stands for configuration file, and that's what it does - configures the firmware. For Anduril, it has driver and light specific settings, and user preferences.
I meant how do you get.that configuration into the light. I have flashed the latest firmware but I have not done any configuration files yet.
Ohh. You probably only flashed a .hex file you got. For a cfg file, you need to compile and link Anduril -- that's what creates a .hex file.
This is what the cfg file for the D4 looks like. file-name: cfg-emisar-d4.h:
// Emisar D4 config options for Anduril
#include "hwdef-Emisar_D4.h"
// ../../bin/level_calc.py 1 65 7135 1 0.8 150
// ... mixed with this:
// ../../bin/level_calc.py 2 150 7135 4 0.33 150 FET 1 10 1500
#define RAMP_LENGTH 150
#define PWM1_LEVELS 1,1,2,2,3,3,4,4,5,6,7,8,9,10,12,13,14,15,17,19,20,22,24,26,29,31,34,36,39,42,45,48,51,55,59,62,66,70,75,79,84,89,93,99,104,110,115,121,127,134,140,147,154,161,168,176,184,192,200,209,217,226,236,245,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0
#define PWM2_LEVELS 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,3,4,5,7,8,9,11,12,14,15,17,19,20,22,24,25,27,29,31,33,35,37,39,41,43,45,48,50,52,55,57,59,62,64,67,70,72,75,78,81,84,87,90,93,96,99,102,105,109,112,115,119,122,126,129,133,137,141,144,148,152,156,160,165,169,173,177,182,186,191,195,200,205,209,214,219,224,229,234,239,244,250,255
#define MAX_1x7135 65
#define HALFSPEED_LEVEL 14
#define QUARTERSPEED_LEVEL 6
#define RAMP_SMOOTH_FLOOR 1
#define RAMP_SMOOTH_CEIL 120
// 10, 28, 46, [65], 83, 101, 120
#define RAMP_DISCRETE_FLOOR 10
#define RAMP_DISCRETE_CEIL RAMP_SMOOTH_CEIL
#define RAMP_DISCRETE_STEPS 7
// optional, makes initial turbo step-down faster so first peak isn't as hot
// the D4 runs very very hot, so be extra careful
//#define THERM_HARD_TURBO_DROP
// stop panicking at ~30% power or ~1200 lm
#define THERM_FASTER_LEVEL 105
// respond to thermal changes faster
#define THERMAL_WARNING_SECONDS 3
#define THERMAL_UPDATE_SPEED 1
#define THERM_PREDICTION_STRENGTH 4