Nope…. When I first got it,it ramped to a point and stopped.no blink.double for turbo.
Now I tried it like you said, and after it ramped through the blink, and hit a ceiling, double click did nothing.
Fixed the steps/ramp
Cell fully charged? Maybe it can’t supply the amperage needed for turbo?
I keep asking because the behavior you describe isn’t even programmable. Its not something you can reset (as far as I know). You’re describing a full-on malfunction. Which is possible, but not easily fixable if its happened.
Charger says 77%
That is exactly what it was. I guess first thing to do besides checking the retaining ring is to reset the temp calibration on these lights.
When unscrewing the tube, and screwing it back on, the light flickers to confirm battery contact. Single click will turn the light on to max single 7135. That’s why he didn’t notice the blink when ramping up. He ramped from blink point. The Emisar D4 does the same.
These multi quotes are confusing….
When I got the light, and started using I ramped up and down a lot. It stopped at a point I would have thought was high, then double tap to turbo…I can only say after loaning it out for the weekend, it’s behaviour has changed. I think
Q? When you first got it it worked, seemingly correctly? Now after loaning out it does not.
Sounds little like someone inadvertently got it into muggle mode. Have you tried clicking it back to normal ramp mode? I’m not home and am not sure of the number of clicks but it is in the user guide
Since we’re seeing a lot of posts about people accidentally getting into muggle mode and not knowing what’s going on, wouldn’t it be simpler if killing the power (by changing the battery or removing the head) put things back to normal?
I know this means that “muggles” could stop the muggle mode. But, let’s face it: they can do that anyway by clicking a bunch of times (6). Clicking a bunch of times is probably something they’d do more often than removing the battery.
Plus, muggles can destroy the light by unscrewing the tail, so you should probably tell them not to take it apart before loaning it to them.
Is killing the power to revert to normal operation really that dangerous?
If removing the battery reset the light that would be a PITA if one likes to use a quarter twist of the head as a lock out. You’d lose the memorized setting.
I thought it was established that that didn’t work for this light
Yes. I know . But pist 10893 proposed using a battery removal to reset. Or did I misunderstand? If I misunderstood, then forget anything I stated.
Now avaiable at Banggood LUMINTOP FW3A XPL HI 2800LM ANDÚRIL UI EDC Taschenlampe EDC LED Taschenlampe Mini L Sale - Banggood Deutschland sold out-arrival notice-arrival notice
Not yet: “Expected on June 14”
A quarter turn of the head locks out the switch, not the standby drain. The standby drain would take nearly 16 years to empty the battery, so that’s hardly a concern.
A quarter turn does not reset momentary mode, as that actually requires interrupting power to the driver.
Looking at the FW3A config file, the highest regulated level is 130 of 150. And that’s the default ceiling level too. Someone may have moved the ceiling.
To reset it to the default ceiling:
- Turn the light on.
- Click 4 times for ramp config mode.
- Click 1 time at the first prompt (it should blink, then flicker… click while it flickers).
- Click 21 times at the second prompt. (151 - 130 = 21 clicks)
Then wait for it to fall out of the menu, and it should be back to the defaults for that ramp. You may also want to switch to the other ramp and change its config too.
LUMINTOP FW3A XPL HI 2800LM ANDÚRIL UI EDC Flashlight EDC LED Flashlight Mini LED Keychain Light Mini Torch 6500KXP-L HI
US$42.99 Preorder
Processing time: Expected to ship after June 14, 2019
That’s how it worked originally… but people wanted it to remember muggle mode after a battery change. So I changed it. Also, it was originally just on/off at one hardcoded brightness level, but people wanted a “training wheels” version of the main UI instead, so I changed it.
TBH, I’d kinda prefer to take out muggle mode entirely. The implementation right now is jank AF. In order to keep people from exiting by accident, it has a bunch of duplicated stuff running independent of the rest of the code. It has its own “off” state, its own LVP handler, its own thermal handler, its own ramp handler, its own boot code, etc… and to reduce code size they’re all scaled down a little more than I’m comfortable with. It’s a mess. It doesn’t interact well with any global features like LVP or tint ramping or a momentary clicky switch.
Even if it means all actions with more than one click will have to turn the light off and back on? That makes it awkward to ramp down, among other things.
I’m planning to add the option anyway, but I’ve been really busy. There’s even a branch which implements this, contributed by zeroflow. It has several other changes included though, and introduces some bugs or side effects, so it doesn’t merge cleanly and I haven’t yet taken the time to refactor it for merging.
Perhaps I should focus on code today instead of BLF.
Hmmm, that pretty well sums it up IMO. :person_facepalming:
By all means… just eliminate it entirely, just as you said you prefer TK. :+1:
TBH I wanted to suggest this……( can not stand muggles) but im was ascared too…. :person_facepalming: