Tuesday, August 12, 2008
Here are a few ideas:
- Use larger resistors
Does that pull–up/down resistor really have to be 1k? Could it be 10k or more? There are always engineering trade–offs to be made. Increasing resistor size increases noise and can make your design more susceptible to EMI, but there are many cases where resistor values can be increased with no discernable effect. Think about this, at 3.3V a 1k resistor will burn up 11mW, change that to 10k and the power consumption drops to 1mW. Your signal line should be in the correct default state (high for a pull–up and low for a pull–down) to ensure no energy is being spuriously expended.
- Turn off unnecessary LEDs
We (I) often use LEDs for debugging purposes, such as internally on an enclosed board. It helps us get some visual information about the system while debugging. Did you remember to turn those off in your release version? LEDs can consume a significant amount of power (1.5V @ 10mA = 15mW) which adds up for each LED that is needlessly left on.
- Dim or blink required LEDs
LEDs that provide visual information to the user can be dimmed or blinked to reduce power consumption. Try to determine whether those LEDs are really necessary in the first place – are there other indicators which are providing the same information? A laptop typically has a power LED and a screen which both provide feedback that it is on, while cellphones have no power indicator other than the screen. Does the laptop really need the power LED to be on all the time? What if it was only on when the screen was turned off, or flashing while in sleep mode? What if the battery indicator flashed when the laptop was off and the battery was full instead of being permanently on? How else can you convey the same information?
- Put microprocessors to sleep
Microprocessors are often waiting for an event such as a timer or communications interrupt. It is normally a simple task to put a device to sleep while it is idle. Some simple code can reduce the power consumption (and extend the battery life) of your device.
- Turn off unnecessary peripherals
Microprocessors usually have a number of peripherals which are either not used, or not used all the time. If unused peripherals are clocked that means that energy is being banished to heat just to clock something that is idle. Not all devices support this, but more and more are coming out with these features (such as the Luminary Micro range).
- Use low power components
Duh! That may seem obvious, but take some time to look at the quiescent current of the components you choose when designing. Faster components (like high speed op–amps) typically require more power when idle, while slower components require less. Consider using a slower op amp or lower power transceiver.
- Use a higher bus voltage
When you are running long wires (e.g. power bus around a warehouse) use the highest voltage that is practical. This will help reduce power loss due to copper losses. It also means you can use thinner cable, or run more units from a single cable (if cable current is a limiting factor).
- Use a lower bus voltage
Have you considered using a lower system voltage (e.g. 1.8V instead of 3.3V)? The limiting factor is often peripherals which require certain voltages, but you can consider other peripherals or use level translators. There are a lot of trade–offs to consider here, so use your engineering wisdom to come up with the best solution.
- Consider latching relays
Normal relays require a continuous current flow to keep them in the on position, while latching relays only require a short pulse to switch from one position to the next. You will have to consider cost and a small amount of extra circuitry, but these are particularly valuable where there are power supply limitations.
Photo courtesy of Windell H. Oskay, www.evilmadscientist.com
Wednesday, August 06, 2008
Thank you for your continued support as readers of this blog. I appreciate your time and attention to read what I put down here, and to make thoughtful comments on it.
Get the latest posts immediately
or enter your email address:
About this blog
About Engineer Simplicity
Engineer Simplicity specialises in the design and development of electronic products.
We are in the middle of an energy crisis and each of us need to make some dramatic changes to ensure that we have electricity, and that the ...
The advert ends with the line, "The walls between art and engineering exist only in our minds." There are a couple of ways to i...
As engineers we spend a lot of time solving problems. A customer has a problem and it needs to be fixed. The electronic boards you have just...
Electronic design automation tools like OrCAD , PADS and Altium Designer are part of an electronic engineer's day–to–day life. We need...
eWaste is a particularly difficult issue to deal with as it contains many different materials and lots of extremely hazardous substances. I...
I was pondering processes while making some tea today. Most of my process pondering these days is inspired by what Sig is doing . I think o...
Load shedding and Eskom have been on the lips of many South Africans over the past few weeks. We have had some of our worst electrical outag...
Every time information is duplicated there is the possiblity of an error. Let me say that again, every time information is duplicated there ...
Mercury in compact fluorescent tubes (CFLs) is a health hazard and therefore we should not use CFLs....at least that is the false message b...
I am an advocate of making sure that every device consumes as little power as possible at all times. Indicator lights should be off, process...
- November (3)
- October (5)
- September (1)
- July (3)
- June (4)
- May (3)
- April (2)
- March (2)
- February (4)
- January (1)