Does double click to turbo go to turbo in mode sets as well as ramping?
I was able to get narsilm with throttle control working in ramping configuration so i assumed it was working in mode sets. However, today i was testing out the rest of the options and realized the 2x click in mode sets is not working for me. two clicks simply advances the out put two levels. Is this just me or is this the way it works?
I have the ramping mode stopping at 2amps for normal operation of the M3 clone. then a 2x click and “BAM!” IN YOUR FACE 7amp Max turbo. I like it!
Ahh. Ok, thanks. I thought it might be my inability to fast click. So good to know. It means I might still have my freakishly fast reflexes after all. Ch’ chahhh… :laughing:
The batteries were almost depleted the light was already down to ML level
When I turn on strobe it is the full FET brightness
no step down of the strobe is going on its still flashing at max brightness the battery can deliver
I have a feeling LVP will not kick in
already 0.05V dropped, since I started the test
Firmware blinks out 2.8V real cell voltage 2.96V
OK I got now the confirmation, driver blinks out 2.7V and in normal operation the light shuts down
Strobe is still going strong and depletes the cells
Your right, when you click and hold it goes to turbo first, then strobe, then the menu. I don’t have my lights right now, so I had to look at my own videos. Lol
I’m not a fan of mode sets. I learned them for the videos, but have appearantly forgot some stuff already.
I looked through the code just now to see how it handles LVP. It appears to have cases to handle ramping and mode sets, but nothing else. It sets LowBattSignal when LVP should happen, but doesn’t do anything with it when the light is in any mode except ramping or mode sets.
The method I normally use is a bit different. In regular steady modes, it drops output or shuts off, similar to Narsil. In strobey modes it “steps down” to a low steady mode, then follows the same drop/off pattern as before. In any other mode (like battcheck), it just shuts off.
I dont konw if i would call it turbo as if the max fet level in mode sets is set under max, it will go to that level. so the clickhold goes to the highest level in that mode set. It will not go to full turbo 255 pwm though. I supose its a matter of symantics.
So when the user needs battcheck you shut it off?
That’s like the range calculator in my RENAULT. It goes down till 80km than its dead. o_O
I don’t need a value for range when the gas tank is full. I need it when I want to know can I reach the gas station 15km away.
The idea is to avoid over-discharging the cells, since if they get too low they can be permanently damaged or destroyed.
It’ll blink out voltage until it drops below 2.9V (about 99.9% empty), and then it shuts off. It’d be like if your Renault gave estimates down to 0.5km before it shut off the engine to avoid damaging the fuel tank.
If the user turns it back on, it’ll blink out voltage again, but may shut off after 6+ seconds if the voltage stays low.
I got a guy reporting, that if NarsilM is set to Turbo when powering on that with thermal stepdown enabled the light steps down after half a second
Here are the videos. I set my camera to have ISO and shutter speed locked. This is while turning the light on from the tail cap. It behaves normally when turning on the light via the front button.
With thermal stepdown disabled (no visible drop in light.)
With thermal stepdown enabled (sharp drop after about 1/2 second).
