Maybe you can send me the source code you have? I assume you configured/set it up yourself?
You really, really need the raptor claw 7135's - I don't trust any other out there, but what you have happening - not sure if that's the problem.
I assume you have the Mateminco from Alibaba or taobao?
Again -- I would only use raptor claw 7135's, but also with this super high amps, I would only use FET+1 designs, never a 3 channel design - these 7135's can't take it. DEL has proposed using a C3 and C4 cap as well to handle spike from the FET hitting the 7135's. Our simple designs actually don't run the 7135's properly to the spec.
Truthfully if you can't get the raptorclaw 7135's, I would use only one channel for this light - the 404 FET, or maybe the better Hyperion.
Uhhh, well, it has to be configured for your driver. It's a very flexible driver, supporting several configurations, but has to be configured for the driver. So you just used the .HEX from the download? Then that's for a FET+1 driver, like the BLF Q8 - the HEX file won't work.
Let me review the driver - I could post up a HEX file pre-compiled for this driver, I think... Let me check.
The raptorclaw is the 7135 in the upper right - the symbol looks like an eagle claw, or raptor claw. The sailboat (bad one) is in the upper left - symbol looks like a sailboat.
steel - I assume you can download and program, but you can't compile the code? You don't have the Atmel studio installed?
I’m not sure how related those comments can be regarding NarsilM…
I just had my first experience with a Narsil based UI - a stripped down ramping only version as i understand, with the Emisar D4 and i have a few issues. Here is what i reported in the D4 thread:
On a similar note, while ramping i can double click to turbo, but then the only option is to ramp back down. I would have expected a single click to go back to the previous level.
Once again i’ve no idea whether this is relevant to NarsilM which i haven’t had the chance to try. Waiting for the Q8 and FW3A…
I developed the D4 firmware under a pretty strict set of requirements. With NarsilM, I don't have any restrictions. When ramping was added, there was a great deal of discussions goin on the BLF Q8 thread on it, so I implemented a lot of those suggestions, most of them, including that turbo and moon won't be "remembered", unless you ramp to them.
A double-click goes to turbo, and another double-click goes back to the previous level.
On the D4, if you single-click at turbo, it shuts off and remembers turbo as your memorized mode. But on my newer stuff, turbo and moon are only remembered if you manually ramp to them. And NarsilM has done it that way for months.
More generally, NarsilM is a newer, upgraded version of the D4 code which does almost everything better. I added a few things to the D4 which aren’t in NarsilM yet, but not much.
@Tom & TK: thanks for the answers. I was just providing my limited experience feedback about the D4… Glad to hear those issues have been ironed out. :+1:
Still, i believe ramping should be constrained to the ‘safe range’ - where the light will handle the heat. Turbo should be an extra step the user decides to take for a short lapse of time - not something you run into just because you keep you finger pressed on the switch half a second too long.
That's probably a sympton of the 7135, the worse 7135's don't do well at low PWM's. In my 16X XHP50 light, the low PWM's work fine in lighting up all 16 LED's. I'm working right now on a similar setup - the MT03, 3 XHP70.2's and this driver: https://budgetlightforum.com/t/-/40540/67.