OTOH, customs really seems to like packages with weird-looking sharp things inside. I’ve gotten two packages with pogo pin adapters, and both were opened by customs to figure out WTF the weird-looking thing inside was. So that might make things interesting for anyone who tries to sell such a thing.
They also seem to be somewhat difficult to make, since the soldering is very precise and involves both sides of the board.
If it’s behaving well, you shouldn’t need to change anything.
If it’s regulating down too early or too late for your taste, then you might want to do new thermal calibration. It’s a bit of a pain to fine-tune on the original D4 though, since it’s just “hold until hot” and the value it picks is subject to quite a bit of randomness… so it can take a few tries.
So if it’s behaving well enough, I’d probably just leave it as-is.
What was the original maximum for this? I cant remember if it was 100% on my Q8 or if I was tinkering with the code. I kinda like having full blast lightning mode.
FWIW, I think the D18 might actually still ship with muggle mode. That might change next time he makes a batch of drivers though.
About lightning mode, there was a bug where it could only go up to level 143/150. That’s fixed now, and it can go up to 150/150. The actual values are totally random though, so I doubt anyone would even notice a difference.
I believe I figured out I have the v2 software - that’s still the “original D4” though?
After the tailcap is loosened and tightened, one click gives a fairly bright output, then holding the button makes it ramp up to astoundingly bright.
In other news, still trying to unscrew the bezel without scraping off the green coating (which came off quite easily when/where I removed the pocket clip)
LOL, that’s ridiculous, muggle mode is (imho) one of the most actually practical features of the Anduril UI and would be the only reason I would take it over Ramping IOSV2 in a D4. There is no sense removing it since it’s quit deeply hidden and accidental activation is impossible.
I agree, especially on these small lights. Right now I just use the stepped ramp for lower output, but its easy to figure out how to switch.
Personally I wish momentary was better hidden since it needs power disconnected to be disabled. Something impossible to do accidentally like 8 clicks vs sandwiching it between lockout and muggle.
So… I was a bit of an idiot and forgot to remove the cell when swapping the mcpcb. I managed to short the LED+ to the body for a fraction of second. Everything worked fine, but the regulated modes were much lower; moonlight was the brightness when doing a diode test with a multimeter. The 100% 7135 mode was about half as bright as it should be. FET modes are completely fine, as are all the blinkies & such.
Anyway, I’ve replaced the 7135 and I’ve still got the exact same problem. I was thinking it could be the attiny chip, but all the software features work. Any ideas?
wondering if one of the resistors got fried, and the 7135 is not getting fully enabled? If you can measure the resistance and its higher than marked on the part, that would suggest something. Of course if the resistance is lower, than its hard to say if there’s a parallel path somewhere causing that.
Yes, the version with RampingIOS V2 is the “original D4”. RampingIOS V1 was only shipped on a small handful of lights, so it was basically an unplanned beta test.
That’s odd. The D4 bezel normally comes off really easily, just by grabbing it and twisting.