contractor - thanks for clarifying. And yes, the 30Q was the first thing I grabbed from my desk. Am now charging a Sanyo NCR18650GA to start proper use of the light.
Could you direct me towards info about disabling the FET please?
JaredM - I was contemplating the workaround to avoid frying the W1 and was going to settle on just avoiding Turbo use. But perhaps can disable the FET as mentioned. Would the W2 not also be vulnerable to being fried with FET (although less so than W1)?
Although I will get a lot enjoyment from the 3 Lume1âs that I have bought, I do wonder if the next step could be a 5A constant current driver for the FWxx. Perhaps thereâs a reason loneoceans settled at 3A cc.
Heat management, space limitations, and cost are likely the answer⌠the first being most important imo. Thereâs little point to create a driver that can sustain 5A in a light that can only sustain 2-3. I donât think white flats in an FW1A was considered a popular configuration either. Of course loneoceans can fill in the blanks thereâŚ
Two ways of disabling the FET are via firmware or physical desoldering. On this driver, is only recommended the first option.
The W2.2 is available from Simon/convoy/AE and likely can take turbo from a high capacity cell and thin/longer emitter wires. It is just as sensitive, but the higher current allows the resistance in the light/connections to burn off more voltage⌠with an older high capacity cell used for a minute at 3A prior, I bet itâs just about right.
JaredM, the W2.2 you refer to, is this the 4040 larger package version of the W2 with that fancy high power name?
Just trying to make sure there isnt something else im not aware of
If there is interest, I could add a no-FET build and possibly a version which uses the FET for more than one level. But first I should probably confirm that the base config works.
A no FET build would be amazing! Will save me 4 days trying to work out how to do it myself.
Great for my custom E21a builds. Ive seen tiny smoke before when ive grabbed the wrong light
A Buck/Boost E21a with a 18500 tube is the dream!
Hopefully there isnt actually a technical limitation to PWM FET as discussed before.
Ive got even more 219b FW3As than e21a, though often im using the 18500 2000mah cells which do a good job already without the PWM.
Yes. Unfortunately due to the nature of the slightly complicated naming convention that osram uses, a few shorthand ways of referring to these emitters have come about. W2.2 = 2mm² 4040 aka Boost HX aka HX aka CULPM1⌠Iâm sure there are more.
Yes it difficult to remember the codes. Owebon made an excellent graphic guide.
.TG = White (6000K-65000K)
.23 = Red (612-630nm)
.14 = Blue (450-480nm)
.13 = True Green (513-545nm)
.F1 = Pure Green (554-566nm)
.FY = Yellow/Amber (580-595)
If you determine more than one level for the FET is workable, then awesome. However, if you try it out and observe unexpected behavior, be aware of the following, taken from the datasheet (page 13):
A no FET and a patial - PWM FET, if technically possible, would be great for people that use 219b. Unless full FET is deemed safe for a 219b setup with this driver.
A no FET and a patial - PWM FET, if technically possible, would be great for people that use 219b. Unless full FET is deemed safe for a 219b setup with this driver.
[/quote]
Actually, if you noticed, I've been running my original Lume1 build in a FW3C, with the 219B 'rosy' LEDs since the beginning of this project, and I haven't had any issues with Turbo mode at all (direct FET drive). However, I did make sure to reflow the LEDs as well as possible, and I made sure heat-sinking between the MCPCB and copper shelf was good by removing any burrs I found on the shelf, and replacing the thermal paste with a good quality one.
In fact, I usually do out-of-flashlight tests with a single Cree XML LED on a large heatsink - I found that Turbo on that single LED actually leads to phosphor damage. I can't guarantee that your 219B setup will work with direct drive, but it certainly hasn't caused any issues for me in my FW3C. I use a Samsung 30Q (pink) battery for this flashlight.
Huge thanks to ToyKeeper for rolling in the Lume1 modifications to Anduril2! I'll get started testing it out, and I'll be happy to provide config files for disabling the FET - this is indeed the easiest thing to do if you want to remove the Turbo feature.
For PWMing the FET, the Lume1 driver uses a tiny charge pump to drive the FET gate, resulting in a high performance Turbo drive. However, this causes a limitation in FET PWM which while not affecting things like 'party strobe' or 'tactical strobing', will limit the ability to PWM at high frequencies. As a result I do not recommend having PWMing on the FET, even though it is possible (with reduced PWM frequency) - this will require some config lines the config files to change the TCPWM for the FET line.
Finally, you all are also right that there is currently no software support for the four aux solder pads. I think it's worth playing around with the firmware to see if I can enable those solder pads to enable easy changing of features - at least disabling / enabling direct drive.
I always reflow the LEDs very well, making sure they have a perfect contact and no excess solder underneath. I use high quality PC CPU thermal paste. I have not used my FW3x lights on Turbo a lot, but the original FW3A used to be an XP-L and I have 219b emitters on it for ages, with the firmware it came with - no issues.
It seems like good reflowing and good thermal paste do make a difference.
I am now wondering if it is worth it losing the FET altogether, since PWM on the FET is not good. I will probably keep the lights running full FET
. Mine are stuck in slow covid chinese mail though 
