6. Batch "TA" 1S or 2S Bistro HD OTSM/NarsilM drivers 15-47.5mm size fit, S2+, C8, H03, MF01, MT03, Q8 Clicky or E-switch

It’s a .png file. An image.

yes of course full address should be hidden

I had it one time shipping stuff to the wrong address, so better check it there

For future reference of anyone reading this and having the same problem as me: I don’t know why I couldn’t flash the bare MCUs when I tried the first time, but I can now. The problem was definitely just a dead MCU on that driver. I’m guessing I killed it when I bridged LED negative to ground. Use your multimeters folks. Everything is fine and well and running smoothly with my lights, sorry for clogging up this thread haha.

I had also a few MCUs killed while using the SOIC clip, bad connection while flashing and it went dead

Received my two LX1 drivers yesterday :smiley:
Finally my 2D Maglite can shine again !
Now, what to do with the second one ?:-p

Hello again. I have a question. I paired one of your drivers I built with the stock emitter from the H03, and separately, with a 219C, both work fine. But when I pair it with an LH351D, it also works fine, but it glows ever so faintly when it should be off. It doesn’t matter if it’s in lockout mode or just off, when the battery is connected, it glows extremely faintly. When the battery is disconnected, the light continues to glow for a couple seconds before going out.

I’ve isolated the issue to the driver itself, it happens on both ones I built. I haven’t been able to test the ones you built, they are in lights that I gave to friends out of town.

I took the drivers out of the light, disconnected all wires but the LED wires. I’ve tried it with several different LEDs of different types, 219C, XML2, and the LH351D.

The light is so faint, I’m sure the standby time is still extremely long, but I can’t imagine this is normal? What could be wrong that’s causing this? What is special about the LH351D that the other emitters aren’t glowing?

As always thanks for all the help.

Ah, good to hear that I'm not the only one.

I messaged Lexel about that and he gave me the advice of cleaning the driver. Sadly that didn't work.

What's pretty clear is, that there is some leakage current somewhere in the path. And considering how the LED is connected, it needs to be somewhere in the negative path as the positive is directly connected.

Furthermore, I tried running the driver outside the host with the LED still connected to rule out any leakage current through the MCPCB or the host itself.

In that case, the LED still has a dim glow, so I would rule out the MCPCB and Host.

So now, on the driver, the following things are connected to LED-:

  • MOSFET
  • Bank of 7135 chips on the bottom
  • Single 7135 chip on the top
  • (The driver PCB itself)

The MOSFET should be a BSC009NE2LS5I which has a diagram for drain-source leakage current in it.

In the diagram, I see that a Vds between 3..4V at room temperature would yield around 30µA of current (If I'm not mistaken)

That's not much, but maybe that's enough for the LED to light up.

Maybe if I have too much time, I will desolder the FET and see if the AMC7135s also have a leakage current.

Another option would be someone with a low value current source who could test at which level the LH351D start a dim glow.

Oh good, same haha, I worried I screwed something up (which I suppose could still be).

I don't think it's so bad aesthetically. I almost like it, if it's not draining my battery more than any other emitter would. More on that below.

And functionally not terrible, especially if the emitter is just capable of turning on at extremely low currents, right? Because that would mean it's not using more current than a different emitter would be, it just so happens to be lighting up with that current. I suppose that would need to be tested.

Anywho, to see if it's the fet or the AMCs, couldn't we just desolder the components off of each channel, or even the lower AMC bank one at a time and see if that changes things? Not the most scientific, but just maybe haha.

PM sent on a couple drivers.

Hey Lexel, check your messages. I need quote on a couple drivers.
Do you take paypal?

He does use PayPal.

I sent you a couple of PMs too, can you respond when you get a chance?

Quick update, I got my hands on one of the lights I modded with the prebuilt driver you sent me Lexel, and I swapped an LH351D into it, and it still does the faint glow. Does it in the light, and set up by itself. So I think we’ve ruled out user error? Very odd.

Hope I don’t come off as upset, or demanding answers. It’s just a curious thing. I haven’t measured the standby current, but I’m not too worried about it.

Did you also try cleaning off any leftover flux than might be causing a tiny circuit? Like brush it with alcohol?

I have not, although zeroflow did, or at least he states he cleaned them. I would assume with alcohol.

I will clean mine as well, for completeness, and come back.

Yes, it was cleaned 3 times.

1) KONTAKT LR Leiterplattenreiniger, clean & brush around the soldered wires

2) Isopropyl alcohol, 99.9%, submerge and brush both sides of the driver

3) Again KONTAKT LR with lots of solvent and lots of brushing

While powering the driver when it was not fully dried did increase the brightness when off

Even after letting it dry correctly, step 2 and 3 did not decrease the brightness.

As mentioned before: I suspect the combination of the MOSFET and LH351D as the culprit.

Okay, cleaning was worth a try. Its free and easy.

Has anyone heard from lexel? He hasn’t responded to my pm in over a week.

Maybe he got some complications with his hand ?

From yesterday: