Update Oct 3: PD68 TripleDown/TripleStack - Tri-Channel Driver

Yes

May be I don`t understand smth, but where I can get full components list? Is it standart and needs only pcb, some parts kit like 17/20/22/30mm FET+7135 Driver DIY Parts Kit - Single-Sided LFPAK and several extra parts with MCU re-programming?

Yes, that parts kit is most of it. It’s just missing the extra 7135’s and you will need to reprogram the mcu like you said

Is there someone subscribed to this thread who could help me on a driver mod? I plan on doing some testing today, but would really like some more input before I do. I am attempting to use the battery indicator circuit from one driver and connect it to another.
The details are here: Nanjg 105c + Lumodrv + voltage indicator on switch Help Updated?

Sorry to poke my nose into this thread. If this is not appropriate, I appologize and please delete or disregard my post.

Thank you all…

In my Blue S2+ (link in Sig) I used the Rev 2 board, but it isn’t perfect so I made this one to swap into the S2+. This one won’t have a ton of uses, but it will work if you want to copy what I did.

TripleDown Rev3 on Oshpark

The adapted STAR momentary firmware is ready for some testing. Patch is here . Compiled firmware is here .

This is of course completely untested but I think I was careful :slight_smile: It’s late as time ran away during some interesting R&D so I won’t be writing a manual. Hopefully the comments are enough. If not, feel free to ask about anything you don’t understand in there.

Oh and in case you’re not used to patches: put it in a file (say, SM.patch) and run something like “patch -p1 < SM.patch”.

Thanks! I’ll hopefully be able to try it tomorrow evening.

I’m going need some hand holding on the “patch” part though. I’m used to the way STAR was originally, I haven’t even figured out TK’s config files yet

It doesn’t appear to use any of those config files. At least not the version I started from.

And a patch is just the difference between the original code and the new version, which is more compact than relisting the whole thing. But if you have trouble with it, this is the whole source.

Finally got a chance to build a driver and test this tonight, sorry for the delay.

It’s very close! For the most part it functions correctly, but the turbo timer steps down when channel 1 is at ‘255’ and it doesn’t step down on the new ‘Turbo/254’ (when the FET is on.) I haven’t tested any lvp function yet, maybe tomorrow.

No worries, I have my own firmware project to keep my busy. And kids. And work. etc :] So take all the time you need, I’ll still be around to fix bugs.

I always forget the simplest things :frowning: Got it fixed and updated.

The modified STAR dual switch could use some testing. Source is here and compiled firmware here .

The SRAM is nearly full because of the way the eeprom is read so you can add at most one extra mode. This looks easy enough to fix but I’d prefer if you tested this version before I introduce more potential problems.

The whole thing is now eerily similar to the STAR momentary code.

Edit: STAR dual switch seems to have buggy low voltage protection, at least from reading the code. It looks like it will step down from low to turbo. Better be careful with it in its current state.

Awesome. Should have time to try it tomorrow.

I ordered this board some time ago and today completed the driver with one 7135 on top and three 7135 chips on the bottom. I used the firmware in the OP and tweaked the values so that now I have moon, low, 0.35A, 1.4A (using all 7135 chips) and turbo.
Really like it that way, the last three modes are all without pwm.

Now I just need to adjust the turbo timer because it is set really low at 5 seconds in the firmware in the OP.

I’m glad someone else gave it a shot! I have them in a few lights now, and I’m really liking them. e-switch and dual-switch firmware adaptations are in the works (possible already done, I just have been to busy to properly test them).

I have the boards and all the parts and I’m in need of some drivers(mostly e-switch). I’m also set up to flash the chips but I haven’t learned how to do so yet. I have the programmer and the program’s downloaded to my PC so I hope any day I will be able to give it a try.

Has anyone else had difficulties with the 7135’s control pin bridging across to the big FET pad / LED- pad? Those two are just a hair apart from each other on the 17mm designs.

Are you saying you have had issues with it, you are you just looking at the Oshpark renders? There’s about 3x more gap than Oshpark shows (though it is still tight). I have only built 2-3 but haven’t had any issues.

Someone built a few and sent me one to get code running on, and there’s a solder bridge where I highlighted in purple. Looking at it in person, it looks difficult to not bridge there:

I’ve tried to remove solder, which didn’t help. Tried to cut it, but perhaps I need to cut deeper. So far, MCU pin 5 still tests positive for continuity with LED-, so when I power it up the LED turns on at a low mode and I can’t flash the firmware.

Sounds like it was hand-soldered perhaps. I would remove the FET and 7135 and suck all the solder off the pads, then reflow with just a little paste under that pin.

Or maybe the board is damaged or misprinted.

I did a little more cutting and it works now. It seems what I needed was an old x-acto blade with a broken tip and very very dull edge to force the extra solder out of the way. Previously I had only tried with a sharp one, which didn’t help.