The Art of Engineering

There are lots of really complicated and difficult ways to design for lower energy consumption, but most of us do not have the time or budget to do them. Yet, there are many really simple ways to reduce energy consumption which only take a few moments of our time. It is largely a matter of being conscience of the decisions we are making.

Here are a few ideas:

1. 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.

2. 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.

3. 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?

4. 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.

5. 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).

6. 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.

7. 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).

8. 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.

9. 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.

These are all really simple ideas, many of which can be quickly and easily implemented. By being conscience of power consumption and the decisions you make you can help to reduce waste and create a cleaner, better world.

Photo courtesy of Windell H. Oskay, www.evilmadscientist.com

I have been very fortunate to have been added to Alltop's engineering page (well, I asked and I received), as well as being listed at #16 on the top engineering blogs on EngineerJobs. My goal is to be in the top 5.

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.

We need three planets for everyone to live like the average European. In other words, if we continue on our current path two out of three people are going to die. In a world of more than six billion people, that is going to be an awful lot of pain.

Will you be one of those who has to die? Your wife? Children? Friends?

So instead of carrying on along a path that will eventually end in heartache, I am going to choose a more difficult way.

I am volunteering to die.

This requires more than resolve and determination – this requires action. It means I have to push against the tide, to take some steps along a less trodden path.

Even though this may appear to be a great self–sacrifice, this is about creating a new life. A new life which enables each of us to have access to clean air, clean water, and nutritious food while nurturing our home (our planet) instead of sucking it dry. It is about acknowledging that we can all live a great life by learning how to live with just one planet, by cutting off and putting to death that part of us which lives like there are three (or more) planets. That is what I am volunteering to do.

The "good life" that has been sold to us is one where we take no responsibility for its consequences. It is a life that consumes with indifference and wastes without thought. Living like that is like extending your mortgage loan more and more each month, eventually the money runs dry and the bank manager comes to collect on the debt by taking your home away. I would rather figure out how to keep my home.

The exciting thing is that this is not about saving the Riverine Rabbit (even though that is important, because we are all connected) – this is about creating better, happier and more fulfilling lives. It is about climbing off the work–spend–work hamster wheel and finding satisfaction beyond the consumption of stuff.

Even though the "good life" we have been sold may be an illusion, putting that to death is a slow, complicated and sometimes painful process. The sooner we can do it though, the sooner we will be able to live a new revitalised life.

"Just as obesity is best overcome by adopting a nutritious, varied, tasty diet and a healthier lifestyle, so too our global overconsumption will be solved by moving to different – but better, healthier and happier – ways of living." – A One Planet Future (worth a read)

Here are some ways to start right now.

Picture courtesty of the WWF One Planet Future campaign

Sometimes we have to say No.

Saying No is an important part – a critical part – or our job as engineers and designers. Great products are designed by people who know when to say No and when to say Yes.

Great products do not need feature lists and check boxes. Great products are sold by their users because they love them.

You know what the most difficult thing about this is? You have to choose, and choosing means you have to be brave.

I just love this graph from Kathy Sierra and the article that goes with it (thanks for the inspiration).

"Give users what they actually want, not what they say they want. And whatever you do, don't give them new features just because your competitors have them!" – Kathy Sierra

There are a lot of steps to turn an idea into a product. Each step requires care and attention to ensure that the best product is created. Below is the process that I follow to create an electronic product. It is all laid out nicely in a linear way, but in reality a lot of the steps are occurring in parallel. Also, any step could be the starting point, it is really dependant on the product and client requirements.

1. Initial engineering report
   

   This is a short report which gives everyone some preliminary ideas to work from. I like to start with this as it is a small investment in testing the idea, and provides a lot of information for the path forward.

2. Detailed investigation
   

   The initial report or specification has already identified the options, now all the options are investigated in detail. This entails reading datasheets and application notes, speaking to distributors, and really understanding whether the available options will provide the required solution.

3. Development of proof of concept
   

   There are two ways to go here, either develop a proof of concept using evaluation boards, or dive straight into the custom hardware design – which is better depends on the risks involved. The risks are a function of the project and the amount of experience with similar designs. Wherever possible it is nicest to speed things up, but a detailed proof of concept can take a lot of risk out of the later stages.

4. Final concept
   

   After a full proof of concept it is quite clear how all the pieces fit together. At this stage we should have system block diagrams, communication protocols, component choices, disposal planning and a whole lot more down on paper. The framework for our creation is in place, now we need to make a real prototype.

5. Schematic layout
   

   All the concepts and ideas have to be put down into technical drawings (an electronic drawing is called a schematic). Once this is done we have a schematic, a BOM (bill of materials), and other technical files needed for the next steps.

6. Printed circuit board layout
   

   The schematic output is used to generate a printed circuit board (PCB layout). The physical size is determined and the components are placed and connected together with tracks. Any mechanical design which is required (e.g. a casing) is also done along side with this step so that the PCB will fit nicely. This can be a time consuming step, as a lot of checking is required, such as tolerances, spacing and component patterns. A set of gerber files are generated which are used to manufacture the actual PCBs.

7. Component procurement
   

   Before a prototype can be built, you need all the components that will be placed on the PCB. This step is really happening in parallel with all the other steps to ensure that everything arrives at the right time. Electronic component lead times can vary significantly (from 1 to 16 weeks or more), so a fair amount of planning and scheduling is required.

8. Prototype manufacturing
   

   A PCB manufacturer (such as WHCircuit or Trax) makes the PCB's according to the gerber files. The PCB is then populated with the components either by hand or machine. For a first prototype I like to populate the board by hand (where possible) so that I can test each part of the system as I build it up.

9. Development and debugging
   

   The amount of effort that goes into making a system work properly is really quite big, but depends on the complexity of the system and the amount of detail that went into all the proceeding steps. It must be shown that each block of the system works and that it all works together properly. Firmware (software that runs on the system) must be tested and developed to a fully functional level. Any bugs that are detected need to be resolved and noted for the future.

10. Testing
    

    Once all the functionality is working it must be fully tested, both to check that it is working correctly and to also stress the system to find out if any real world events could break things. Careful attention must be paid to test as many usage cases as possible, and more. Certain countries require specific certifications and any required tests must be done to ensure all the necessary specifications are met.

11. Design refinements
    

    All of the testing and development will either have proved that the design works exactly as desired, or indicated areas that need to be improved before going ahead with manufacturing. Steps 4 to 11 are repeated until the product meets the requirement.

12. Initial production run
    

    Manufacturing can bring its own challenges to the product from solderability through to the programming and testing of the product. To avoid major manufacturing disasters it is normally better to have a small initial run to iron out any problems in the process.

13. Product manufacturing
    

    Once all the manufacturing issues have been resolved it is time to go into full production. This can be a big investment and the quality of the work that has gone before will determine how successful the product is.

14. Continuous improvements
    

    There are always things to improve. Wherever possible I try to build in mechanisms that allow easy upgrading of products (such as in–field upgrading of firmware), but it is sometimes necessary to go through some redesign to meet a new requirement or fix a manufacturing issue. Once a product is out in the field you start to get a feel for how it is really used, which teaches you a lot about how to improve the quality.

It is a long process and is fraught with many risks, but the great reward of having created something meaningful which changes people's lives for the better is amazing.

If you are interested in creating electronic products, then please contact me.

Photo courtesty of Johannes Henseler and licensed under a Creative Commons license.