[quote=pol77]
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.