NUD4001, Dimming Demonstration Board demonstrates this circuit. It can be built with an external transistor to handle voltages up to 18 V (instead of 6 V), and it can use either a single LED on the board or it can connect to an external LED. NUD4001 LED DRIVERS FOR MAC - Subject to the foregoing, this Agreement shall be binding upon and inure to the benefit of the parties, their successors and assigns. Nothing contained in this Agreement limits a party from filing a truthful complaint, or the party's ability to communicate directly to, or otherwise participate in either: The. We have real consumer drlver of different types of bp led driver, bp3102 led bushing driver reviews, cable drivers reviews and more. Number of Employees 11 to 25 People. LED Driver Our range of products include led driver 7w ma, 12 vdc led bulb, bp led driver, bpa led driver, bp integrated circuits and bp3102 led led driver.
I'm hoping someone here has some experience with the (16 channel, I2c interface). So far everything is working pretty well after getting the circuit connected properly. I'm using a to drive this. The PCA9685 allowed for a PWM frequency of between 40Hz and about 1500Hz. The default is 200Hz.
After setting this frequency, I can choose the pulse on and pulse off interval anywhere from 0-4096 (which is the pulse resolution). So if I want the LED on full brightness, I can set On=0 and Off=4095. This works fine and I get a nice solid LED. However if I start to dim one of the LEDs to say 25% of it's brightness, I'll set the On=0, Off=1000. This dims the LED but sometimes it starts to flicker.
I've tried a lot of different combinations of On/Off times and PWM frequencies. Even at 1000Hz it is flickering, and it gets worse when I start to use all 3 RGB components. I'm driving the Picobuck with a seperate 12V DC source, and it has a heatsink. Do I need a resistor or a capacitor somewhere in the circuit to stop the flickering? All I'm trying to do is get the LED dimmable from 0-100% without any flicker, so I can combine the red, green and blue colors. Here is a picture of the setup, there are no extra components - just PCA9685 board, Picobuck and the RGB LED.
The red/black wires off the Picobuck are going to a seperate 12V DC supply. What am I doing wrong? I've had the same problem as the OP and found on the NXP forums which describes my problem (and I think the OP's problem?) well. In any case this ESE page is one of the first sites that appears when searching for PCA9685 flickering LEDs, so I thought I'd add my solution here.
From the NXP forum: Looking at the datasheet fig. 11 on page 20 this looks according to design, the problem is whenever LEDnON LEDnOFF and the LEDnOFF register is updated, the device skips one whole output phase, switching the output off regardless of the registers - look at the empty cycle between 'register(s) updated in this cycle' and 'output(s) updated in this cycle'. There's no empty cycle when LEDnON. From the page you linked for your PicoBuck: This PicoBuck supports PWM control so long as the signal is above a minimum of 1.5V and each LED is driven to 350mA. What might be happening here is that there is a capacitance (either an intentional cap, or parasitic capacitance.most likely a cap tho) between your square-wave PWM output and the corresponding input to your PicoBuck.
When you turn down the duty cycle to get the really low outputs, it can take multiple pulses to sufficiently charge the cap to =1.5V. This can effectively form another oscillator (similar to a sawtooth osc) where the cap charges for several pulse cycles before reaching the PicoBuck's threshold voltage & 'tripping' the PicoBuck to flash the LED, down to a low enough frequency to cause visible flashing as the duty cycle reaches low enough values.
Possible fixes:. If there's an easily removable capacitor on your PWM output, remove it (or at least replace with one of significantly lower value).
Try adding an NPN & a schmitt trigger/P-FET (or an op-amp with high voltage multiplier) between the PWM output & the PicoBuck's input to 'square up' the signal waveform to as close as possible to a clean +5V/0V square wave, low-impedance signal. Here's an example using about $2 worth of components per LED:. Check for supply voltage irregularities in either your PWM controller's supply pins, or the same for the PicoBuck. I suspect that your notice of 'it getting worse when you use all 3 RGB components' is most likely that it's more noticeable due to proximity/visual comparison, rather that affecting the 'actual' output. However, simce you mentioned it, checking for supply voltage issues would be the first place to look for something that could cause that. There are no other components in the circuit (see the photo I added).
I'm not sure what a Schmitt trigger/P-FET is but I can do some reading and see if that will help. I don't have an oscilloscope to test the square wave with unfortunately.
The 12V supply to the Picobuck is steady as far as a multimeter is concerned, but that's all I know. I am from a software background and finally feel what it must be like for the guys asking questions on there! I'm sorry this is quite new to me, I'm a beginner with electronics. – Feb 20 '16 at 0:26. @Mangist a Scmitt Trigger is a digital device that 'triggers' when its analog input rises or falls past a preset threshold; thus turning a slowly changing input voltage to an abrupt on/off square-wave pattern. A P-FET, P-MOSFET, or P-Channel FET/MOSFET is a type of transistor that's often used as a 'solid state switch' in circuits; when its 'gate' pin voltage is pulled low with respect to the source pin.
I'll add a quick circuit diagram to my answer to help a bit. – Feb 20 '16 at 2:00. Reading the datasheet for AL8805 (the chip in PicoBuck) there's two modes of controlling it: either PWM or a constant control voltage. It's possible that the flickering happens because the chip gets confused which one you're trying to do. Couple of troubleshooting things to try:.
Try the constant control approach: instead of using the PWM driver, whip up 1 V with a voltage divider and use it as the PicoBuck input. How fancy is your multimeter? If it has hold settings for min/max voltage, stick it between GND and IN1 of the PicoBuck and check that the minimum voltage is low enough and the maximum is high enough (see Recommended Operating Conditions in the datasheet). And if it's got True RMS, measure the average voltage to see if it's in the right ballpark.
Experimental: If the constant voltage control works and you can't make PWM work, stick a whooping big capacitor between PicoBuck input and ground, and maybe a small resistor for current limiting. The idea is to smooth the PWM signal into a corresponding control voltage.
Disclaimer: Untested, might fry the PWM controller. Looking at the datasheet it looks unlikely but proceed with caution. The datasheet for reference.
I'm not sure how to whip up 1V with a voltage divider. I am just using the PWM method based on the PCA9685 outputting a PWM @ 3.3V. That should be more than the 1.5V threshold for the Picobuck to accept it as a PWM input.
My multimeter doesn't have those min/max functions, but I do have access to an oscilloscope, except the guy who knows how to use it is away. I'm going to try what you suggest and put a large capacitor between Picobuck and GND. Any suggestion on uF? Wouldn't the capacitor smooth out the PWM signal and defeat the point of using PWM? – Feb 24 '16 at 21:35.