TechOnline India Header
Most Popular
Top 5 Courses
  • Fundamentals of PCB Design
  • Paralleling DC-DC Converters
  • Fundamentals of x86 Architecture
  • Analog Devices' SHARC 32-Bit DSP
  • Analog eLab - Improved INA Input Filter
    Most Popular
    Top 5 Technical Papers
  • ARM Platform Technical Overview
  • Using C++ Efficiently in Embedded Applications
  • Top 10 Drivers for Embedded Android
    Most Popular
    Top 5 Webinars
  • Designing embedded HMIs and connecting them to hardware
  • 2009 Embedded Market Study
    All Articles Products Courses Papers VirtuaLabs Webinars
    Top Search Items
    C


    Techpaper Spotlight

    Wind River
    Accelerating the Development of Embedded Linux Devices with JTAG On-Chip Debugging
    /
        Login | Register | Welcome, Guest

    Topics
    POLL
    How much code have you produced in your career?
    A few KLOC
        38%
    100s of KLOC
        44%
    Millions of LOC
        11%
    A trillion
        7%
     



    Low-power parts vs. low-power design
    Low power is good, but what are the tradeoffs in achieving it.
    Power Management DesignLine
    Low-power ICs and low-power designs are hot these days (of course, we are only speaking figuratively here, not literally). This is not just for "environmental/green" reasons, although that plays a part in it. The simple fact is that low-power designs enable longer product run times from a given battery pack. Even when you are not source-limited and have an AC line in your product, lower power translates into cooler products, which simplifies thermal issues and increases reliability, and has many other system-level benefits as well.

    But how do you achieve low-power results? This does not always have a simple answer. The obvious approach is to use lower-power ICs, higher-value resistors (if you can; lower current = less I2R loss), and other parts which minimize dissipation.

    Sometimes, though, the simple approach is also too simple, and the sum of the parts is not enough to yield the results you need. It may turn out that a higher-dissipation part has better functionality for the project, or has better power-management and sleep-mode operation. Depending on your duty cycle and peak/average/quiescent power needs, a higher-dissipation part may actually reduce overall consumption. Or, you may have an audio amplifier with good efficiency at moderate audio volume, but lower efficiency at the audio levels users will actually use it.

    As with most engineering and design issues, there is no single, simple answer, and judging the tradeoffs is an important part of the challenge. Don't rush to the obvious answer, until you take a little while to think about the question from different angles.♦

    1
     
     
    Latest Webinars
    · The Next Generation of Ethernet: How the New IEEE Standards Enable Energy Efficiency and Quality-of-Service
    · Simplified Physical Layer Receiver Test of Re-timed Architectures Such as USB 3.0, SATA, SAS, PCIe 2
    · How to solve the most common high-speed bus issues in embedded design on a budget
    · Early access to ARM Core Technology with Fast Models from ARM
    · Latest MIPI Standards: PHY and Protocol Testing Guidance
     
    Member Company Spotlight
    GE Intelligent Platforms
     

    Read the latest white paper from GE Intelligent Platforms, "Making Flat Panel Computer Systems Work in Harsh Environments." This paper explains how manufacturers are producing rugged computer systems that bring the simplicity of a Microsoft Windows-based PC to tough field applications. View the paper here.


    Member Companies