My fw3x after just a few seconds of turbo very rapidly ramps down off it only does it with the latest Anduril2 10-25 lume1 firmware. Does anyone else have this problem where turbo doesn’t settle on a stabilized output but just goes off?
I think you have to post the video on a website like YouTube, then use the YouTube link to embed the video here.
Try with another battery see if same issue.
Sorry for the cartoons in the background kiddos got the clicker
I’ve tried different batteries I’ve tried reflashing 10 times I’ve only had luck with older firmwares from 1-25 or the one in July or August but the firmware that is the latest version is the only firmware that does this the other firmwares are completely fine but if I use the older firmware’s I don’t get the updated features and I actually use a few of them
The lume1 doesn’t have any in-between from 3A to full turbo, so the ramp down is quite aggressive.
But when I flashed the earlier version of Anduril 2 the turbo lasted a normal amount of time and then would step down a little bit and stabilize at a pretty bright level but with this latest version it after a few seconds steps down all the way to off and I can’t get a hold of toy keeper and I have no idea how to modify the firmware so I don’t know if this is happening to anyone else or if it’s just my light but it’s a little frustrating. Any ideas?
But if you watch the video it doesn’t go down to a low mode it goes all the way off and like I said with the older firmware I flashed on this exact light it didn’t have that issue turbo lasted a decent amount of time and would step down to a reasonably bright regulated level everything was fine it’s just the latest firmware
I have thermal set all the way up. I’ve calibrated the light to room temperature and set throttling at 70c
I’m facing the exact same issue with the current Anduril2 FW. Turbo for a few seconds and then an aggressive step-down to off. I might have a look at the code and find the commit that introduced this bug.
Lume1 using external calibrated temp sensor. You don’t need to calibrate it. I ques its something wrong with new firmware. Ask Toykeeper about it.
This is broken as of the revision 622, which has commented out the ‘ifdef LED_ENABLE_PIN_LEVEL_MIN’ block (fsm-ramping.c +209).
Seems to only affect the fw3x-lume1, as this is the only target using this as far as I can tell.
@ToyKeeper - I’m not really familiar with the code yet, but simply reenabling it works for the fw3x-lume, not sure about any side-effects for e.g. tint-ramping.
Would you mind to have a look?
Btw, thanks ToyKeeper for the hard work! 
I wish I had seen this before yesterday. I was having the same problems so I built every revision and tested until I reached the same conclusion as you did.
I created a bug report here and sent Toykeeper a Chat on reddit, but no response yet.
Tagging @ToyKeeper
Maybe you can shed some light on what this code block does and why it was commented out?
Thanks for all you do!
Edit: link to the code in question:
https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/anduril2/view/head:/ToyKeeper/spaghetti-monster/fsm-ramping.c#L209