Hello all hoping you can give some insight on the issue I am having with my
MTN-17DDm with guppydrv dual firmware .
Have it in a Convoy C8. Started with XP-L HI and it worked fine. Had voltage and all the mode groups.
Tonight I swap in a XP-G2 dedomed. And headed out for dog walk. I was in mode group 5
15–100 It worked great. I went to 8 click to check the voltage after a few minutes of use and I didn’t get the voltage flashes.
After several attempts to check voltage I ended up in another mode group.
Now home, I can click 8 times. NO Voltage Blinks.
I can click 8 times then click more time and still change the mode groups.
Seams like I have lost the Voltage blinks.
EDIT- went to a beacon mode light doesn’t shot off just pulses ever 4 seconds.
also the moonlight and lows are brighter then they should be
Anyone have this happen ?
Any suggestions ?
Trouble shooting ?
Does not really sound like a short… but if the modes that only use the 7135 are being driven 100% when only the 7135 is used and when the FET is used those are also fully driven it could be a short around the reflector… I am good at making shorts, but have not seen that behavior. There are better troubleshooters here than I am and i am sure they will pick up on the thread soon.
If screwed in, loosen the retaining ring and reseat it, sounds like a bad ground. Also check the negative wire soldered on the pill, I have had some weird results if it grounds out with one of my drivers loaded with guppydrv.
Ok, Tore it down. didn’t see anything wrong were leads were hooked to driver.
soldered back up to led, checked without the reflector in and had same issue.
When set to ml-5-15-50-100% the first three are same brightness.
Thanks for input. I will go check the ground better on the driver.
Seams like the 7135 is maxing out on its levels. Not sure what level it starts using the FET
I have the FET17-SS guppydrv and beacon is: moonlight - flash - moonlight - flash … It doesn’t shut off between flashes. I don’t know if it’s supposed to be that way but it’s fine by me.
Back, tore it down again. Re-did the leads on the board. Lightly touched everything with soldering iron, looked it over with magnifying glass. Tried it with the XPL-HI that was in it.
Same results.
I believe the 7135 chip is giving me max. But somehow I am not getting off on the beacon(which it did before) or completely off on strobe.
The firmware is still working and I can still change mode groups.
Could the 7135 chip be shorted internally ? Shot?
Will be hard to sleep without knowing.
lightme——yes it was off before, a blink every 3-4 seconds.
my strobe doesn’t go comply off.
Just checked and my strobe modes also do moonlight in between flashes. I don’t see it as problem since it’s so dim. Are you sure yours wasn’t doing the same thing as mine but you thought it was off because moonlight was so dim? And now that all your lower modes are the same brightness, it no longer appears off.
Mine jumps from about 150 lumens to 1000 lumens on beacon. Maybe it came that way and I didn’t see it before, have other guppydrv’s that go off on beacon and strobe.
When I 8-tap to go to program/voltage beacon. Mine stays constant brightness. I do not get any flashes for battery voltage. I am not getting any levels below about 150 lumens.
Everything but ML was working all day in the house. Tonight go to walk Red and had issues again. NO ML off and on beacon and strobe , couldn’t get it into any 1 mode group. All over the place.
I’m far from the expert here but it seems to me that some component’s tolerance is out-of-spec or has failed and that could be inside a chip itself. Seems like you’ve covered all the other bases.
Tore it down again tonight. Took spring and leads off. Swapped out the 7135 again.
Really put the heat to every component while pressing hard onto the board.
NOW I have every light level but the ff-ml level.
Anyone know if ff is related to a specific component on the board ?
