Timeline for LED Driver with Overcurrent Protection
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 26, 2017 at 9:35 | vote | accept | m3x1m0m | ||
Jun 26, 2017 at 9:33 | vote | accept | m3x1m0m | ||
Jun 26, 2017 at 9:35 | |||||
Jun 19, 2017 at 10:52 | comment | added | John Meacham | Could you just put a zener on vsig to clamp it to some maximum voltage? Seems like the most straightforward way. | |
Jun 18, 2017 at 22:58 | comment | added | m3x1m0m | My idea is to put the LED driver on its own PCB and maybe someone else is at some point developing a digital board, which is completely independent from this one. I mean it is always kind of obvious, that you should not go beyond 30 mA with 5 mm UV LEDS, but people still burn up LEDs. | |
Jun 18, 2017 at 19:26 | answer | added | WhatRoughBeast | timeline score: 0 | |
Jun 18, 2017 at 18:17 | comment | added | TonyM | Building on @ThePhoton good comment, you would make the DAC full-scale output voltage produce the largest LED current that the application requires and that the LED can continuously handle with no significant difficulty or degradation. The DAC should not be capable of getting the LED damaged, unless the application absolutely requires it. | |
Jun 18, 2017 at 17:58 | comment | added | The Photon | How is the colleague (or software) controlling the input signal? Why not just make sure the scaling from input (DAC or pot) to the op-amp input is reasonable? | |
Jun 18, 2017 at 17:42 | review | First posts | |||
Jun 18, 2017 at 20:16 | |||||
Jun 18, 2017 at 17:40 | history | asked | m3x1m0m | CC BY-SA 3.0 |