Categories
Analog Electronics

The humble indicator LED

I proposed a talk to the Hackaday Superconference yesterday titled,  “Improve your circuit toolbox: Simple designs that will save your next product”.

While I don’t know if the talk will be accepted, I thought it could be a good discussion regardless and thought I could write out some thoughts here. I haven’t been writing much lately and wanted to stretch my muscles again, so why not?

The first circuit on that list will be an indicator LED.

Yep, that simple of a circuit. Allow me to share a diagram:

The power of the blink

All this circuit does is light up. When the user inserts batteries and enables the circuit via a physical switch, the power flows through the regulator and lights up D4 which is a red LED. That’s it.

The crazy thing about this circuit? The LED indicator was not implement until rev 3 of the design! Prior to implementing this I only knew the status of the board when I put a DMM across the power terminals.

Throughout the testing of the above project and in many other projects, I have shorted things out by accident. When there is a power indicator LED on board that starts to blink because I’m dragging down the power rail, it’s easier to stop doing what I’m doing. If that isn’t there, sometimes the only indicator is another part of the circuit communicating intermittently or the switching converter starting to whine.

The serial blink

Arduino users will know this one well, there are LEDs that are attached to the serial lines. When you’re programming the board or transmitting back via the serial console, the indication is obvious.

You need to be careful with your serial lines, ensuring your LEDs don’t pull too hard on the lines. Set your current with the proper sized resistors so you don’t mess up the edges of your serial lines. When in doubt, take them out.

Blink is optional

You don’t need to end up populating these parts when you go to production. Your low power product might not be able to spare the milliamps of current. You can either “turn down” the resistor brightness by using a higher value resistor or you can leave the LED out entirely when you’re certain you have a stable product.

Your eyes are test equipment

While these circuits are super simple, it effectively re-purposes your eyes as test equipment. There is a high amount of light sensitivity in the human eye and even small changes like brightness difference or flicker will showcase that “something is different” if not “something is wrong”.

LED indicators will help you troubleshoot your next product. Be sure to add them to any/all of the following:

  • Input power
  • Output power – After your custom regulation
  • Output power – After regulation happening on a chip or module
  • USB power (if separate from your input power)
  • Battery charging
  • Serial lines
  • Status LEDs

By Chris Gammell

Chris Gammell is an engineer who talks more than most other engineers. He also writes, makes videos and a couple podcasts. While analog electronics happen to be his primary interests, he also dablles in FPGAs and system level design.

4 replies on “The humble indicator LED”

“Your eyes ARE test equipment”! Last night I found another way to use them: plugged FTDI programmer in wrong, had labelled it with a label maker. Heat sensitive dye in the paper label started turning black as it overheated. Putting label paper on all my dev board chips now! If the chips run too hot during normal use, I’ll just find a place for the sticker somewhere nearby or on the underside of the board. Hope this is useful for someone.

I have been designing industrial controllers for over 30 years. I looked at the existing relay logic controllers that I was replacing and noted that it was hard to stand in front of them and see what was happening. When I designed my microprocessor based version, I made sure that all the inputs and outputs had indicator LEDs and the relays that are used have indicator LEDs as well. In addition to the inputs and outputs, I also have indicators on the watchdog timer and serial port. It has paid off big time in ease of troubleshooting. I can even have a field technician text me a picture of the controller, or a video and assist troubleshooting remotely.

Comments are closed.