phalanx wrote:Now I understand. You need a large amount of PWM channels to control 45 3-channel PicoBucks.
Yes, that's exactly what I'm trying to do, sorry if my english didn't expressed it very well.
phalanx wrote:When you say it's working well right now, are you connecting the control pin directly to one of the TLC's output pins?
Yes, it works (almost*) perfectly having it connected directly to the TLC output pins. I was told that I should try to maintain the supply voltage of the TLC below the PicoBucks data input voltage maximum ratings and it should be fine.
phalanx wrote:Since you appear to have it running with a reduced number of LEDs, were there any problems with what you had running or is your concern about scaling this up to your full 135 channels?
Yes, since I'm just starting with the use of microcontrollers and breakout boards (and I have some basic knowledge in electronics) I don't know if there could be a problem, for example, when having all the TLC outputs connected to the PicoBucks.
(*) I'm having a little problem now, maybe you can help me with this too: my code works but the TLC boards are meant to drive common anode RGB LEDs, and the inputs on the PicoBuck are equivalent to a common cathode RGB LED. I worked around this simply by inverting the RGB values in the code (4095-R, 4095-G, 4095-B), but I encountered a problem when the values sent are equal to 4095 ("black" in this inverted logic). The driver acts like the value is 1 instead of 0, and I have a very subtle but very noticeable low light flickering when it is meant to be off. I tried sending values of 4096 with the same results, maybe I should modify something in the TLC libraries? Or there are better solutions to make the convertion from common anode to common cathode using electronics? (I tested with a common anode low power RGB LED, without the inversion and without the PicoBuck and it works perfectly)