Hey guys, got a flashlight itch a few weeks ago and found myself lurking in this forum. I decided to attempt to duplicate this fantastic mod by testedandbaked: Lumintop Tool (AAA) Mod. Literally a straight copy with the only difference being a 5000k 219c. Got everything assembled and flashed but I have some strange behavior from the driver (fet+7135 BLF A6 FW). The light will run and I can cycle up in modes, but middle length presses will not move down in modes (OTC issue?). The light will also step down a mode every few seconds until it shuts off. I’m quite certain the issue is somewhere in my driver but tips on where to look would be appreciated. I have a DMM just not the knowledge to use it in this application. Any help would be appreciated.
Those drivers have issues m8
This i ususaly got this when i burned a resistor while soldering it to the PCB, it happened several times
Seems the resistors are used as part of the LVP. Definitely explains the step down issue. Pretty sure I damaged one of the resistors and the off-time capacitor. I’m assuming the off-time capacitor is used to supply power for a short time after the light is turned off to allow the attiny to figure if it was a short press or a long press. I have spare components so I’ll give it another go. Thanks for the help.
Attempt two ended with the same result. I’m using hot air and was very careful about overheating this time. I also noticed my programmer wouldn’t recognize my attiny until I removed it from the board. Anyone have any other ideas?
This is probably a bit late, but by chance I found this thread and hope this helps. Your issue is likely one of two things. Either the firmware is reading your battery as <3.0v (incorrectly) so it’s stepping down the LED to save battery every few seconds as programmed OR your battery has high internal resistance and is sagging to <3.0v when you are powering it up.
I adjusted the values for battery voltage reading using Toykeeper’s battery calibration firmware and a lab power supply to get the most accurate values for my chip. Perhaps your chip is giving different values.
I have one of these drivers showing exactly the same symptoms as in the first post, any new ideas as to what may be causing it?