Author: 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.

Categories
Engineering

The Engineering Model Of The Future: Malcolm Reynolds

“Wha?”

That’s what you said when you read the title, isn’t it? That’s probably what I would have said. You said that for one of two reasons:

  1. You’ve never watched Firefly.
  2. You’ve watched Firefly and you just don’t get it yet.

The second is more excusable than the first. If you’ve never watched Firefly, I highly suggest going to do that right now. It’s 14 episodes (one season) and a feature length film. It’s a great show that was unfortunately cancelled after one season.

“So what the hell Chris? You’re sounding like a lame fan boy.”

Yes, yes I am. And I loved the show but I love the analogy much more. So let me explain the background on Malcolm Reynolds a bit before I dive into the relevancy to this site and electrical engineering.

Malcolm Reynolds, played by Nathan Fillion

Mal was the captain and owner of the Firefly (a spaceship). Prior to that, he participated in a war between the Alliance and the Browncoats, on the losing side. After the war (and where the show picks up), he is working with a small crew, floating through space and picking up jobs wherever they can. They aren’t always glamorous jobs but they often require ingenuity. Often times, they are avoiding the Alliance, which is a federation of the populated planets. They control just about everything in the galaxy and have very advanced technology. They seek to bring everything under their control.

Starting to see my point? I believe that engineers of the future (and already starting today), have only a couple options:

  1. Be part of the ever growing “Alliance” — In this case, the corporations (companies >200 people) that have an increasing share of the technological population.
  2. Be part of a smaller company (20-200 people). However, I believe that over time these smaller companies will continue to disappear (in the electronics world) because of the difficulty of competing on cost. They will either go out of business, see costs increase to the point of employees leaving (healthcare premiums, anyone?) or will get swallowed up by bigger companies.
  3. Work alone or in very small teams. Work on jobs for smaller companies in a contract situation. This would be where the future engineer is very similar to Malcolm Reynolds.

The corporations mentioned in the first point are large for many reasons, not all bad. One of the most striking is economies of scale; places like a semiconductor fabrication facility simply cannot operate with small budgets. They need capital equipment which is produced at great cost and the company is necessarily big in order to recoup the initial costs. Another is working with very advanced technologies. If you happen to be an engineer that is working with circuits that operate at 10’s to 100’s of GHz, you likely require very advanced equipment in order to monitor and modify your circuits. Only the largest companies will be able to afford the bleeding edge technology required to develop future technologies (i.e. If you’re working on 20 GHz signals, you need a scope that can detect 40 GHz or more in order to see higher order effects). While in Firefly the Alliance wasn’t necessarily big because of these reasons, they were very advanced technologically and were the only places that offered opportunities to work on the bleeding edge.

Now before I take this analogy too far, let me speak to the “stealing” side of Firefly. I think that’s really where it begins to fall apart. Hopefully none of the engineers of the future are taking from the large corporations that represent the Alliance (except maybe the contracts they win). Stealing isn’t right and in the show is usually because of necessity; I would never encourage any engineer to be anything but outstandingly ethical. However, there are situations in the show where the crew of the Firefly work indirectly for the Alliance in hard times, which I think is reasonable. In engineering terms, I imagine a small design firm of the future working on fixtures for a large factory that needs to outsource some work. Or working in conjunction on a project because the small team is a preferred vendor for a particular part of a product (the embedded system in a robot, for example) and the large corporation provides “the rest” (the remainder of the robot and the expensive moving parts, to continue the robot example). These are all plausible situations in the future and even happening today.

To compare engineers and engineering firms of the future to the Firefly crew paints kind of a bleak future (if the analogy is to be believed). It will be hard to find work because much of it will be dominated by larger companies. And why wouldn’t it? The corporations offer more manpower, lower costs and the potential to create larger things. However, all is not lost. Smaller engineering groups can offer many things which also have parallels in the Firefly universe. These are lessons which can be used today and are a reason I liked the analogy so much. Let’s go over how and why a smaller engineering crew might succeed.

  1. The ability to take jobs that larger companies cannot or will not.
    • Large companies may not want to take on jobs that are small and do not provide a likely return on investment (ROI). However, a smaller company may be willing to gamble on these sorts of things. Historically, the smaller ideas have larger risks but much larger rewards, which could be beneficial for a smaller company willing to take on some risk. An example might be a new product idea brought to a smaller engineering company that is radically different or not fully funded. By going into a joint venture and partially funding the project (assuming they believe in it), they could see large payoff. The lesson here is to investigate opportunities, but be willing to take risks that larger companies will not.
    • In the show, this often meant working with unsavory or misunderstood people in society.
  2. Agility in all aspects. Smaller companies are more likely to be able to adapt to situations.
    • This could mean picking up a new piece of software quicker, responding to a customer’s changing needs quicker, not being bogged down with corporate bureaucracy, being able to fly under the radar of larger competitors, really anything that means you have the advantage as the little guy.  The lesson here is to maintain that agility (even if you begin to grow as an organization) in order to succeed.
    • In the show, they had lots of tricks up their sleeves to maneuver around the Alliance, often outrunning them or tricking them when in a tough spot.
  3. Your jobs will be almost entirely referrals.
    • Almost all work is found through connections, either by word of mouth recommendations or prior experience with a customer. It’s important to remember that your reputation as an engineer can lead to future success, so to maintain that like you would any other skill. New work will also be an active social task, either asking current connections who needs help or asking for recommendations. And yes, social media can count as a social activity to find new work, though I would not count on it as the only method of finding work today.
    • In the show, the reputation of the crew got them jobs and respect while continually mobile and moving from planet to planet. They also had to take a few not-so-fun jobs.
  4. Trust the people on your team. And make sure you like them.
    • If you’re working in a small team, the likelihood that you spend more time with them than your family is pretty high. It’s a reality that smaller businesses don’t have structured hours. That’s because much like the Firefly crew, finding work and getting the job done is all you can do to survive. It’s not until you are successful that you can be choosy about which jobs to take and which you don’t. And in the mean time, the job at hand will be very time consuming; so choose your team wisely.
    • In the show the crew was basically like a family and their isolation from others while in space was pretty drastic.
  5. The focus is on completing the job, not necessarily perfection on all fronts.
    • This is exemplified by the scrappy nature of Malcolm Reynolds and his crew and is a necessity for small engineering businesses. When resources and money are tight, the main design constraint is getting the job done. This often means going with proven solutions–so you might start with a reference design or development board instead of trying to start from scratch. This means favoring simplicity and elegance in design solutions over complexity, regardless of how “cool” the complex solution might be. The emphasis on completion can help you plot the fastest course to get to the end of the design, and then focus your energy on removing the obstacles that are guaranteed to pop up (boards are late, can’t get parts, etc).
    • In the show they did what they had to and often improvised in order to get the job done. Also since it was a show luck seemed to favor them a few times…

So there you have it: how I view the future of engineering, especially for those not choosing to work for corporations. Both have their benefits and drawbacks, but I believe the choice between the two will continue to be much more polarized. Those choosing the later and striking out on their own may have hardships along the way, but will be rewarded with the freedom to do what they choose and when they want to do it (with the ultimate restriction being putting food on the table).

I’m sure I could compare engineering to a lot of things, but this one seemed to fit. Did I miss any aspects of being a small engineering business? What do you think?

Categories
Analog Electronics

The Rock Stars of Analog

Over on The Amp Hour, I’ve been known to call ham radio operators, “The Rock Stars of Analog“. This is meant for the ones that are out there making their circuits using the dead bug method or otherwise. Jason Milldrum from NT7s.com has confirmed this belief with a picture in his latest posting about his RF kit making business:

Project X Prototype

I mean would you LOOK at that thing??? It’s awesome! Plus it transmits radio signals, so it’s just that much more magical. I know the theory behind RF, but I still geek out whenever I think about radio stuff. Anyway, thanks to Jason for posting the picture on his site and on Flickr. Check out his blog for more info as it comes available!

Categories
Analog Electronics

What Is A Power Budget?

Boy is it hot in here or is it just me? Why’s that gizmo over there giving off so much heat?

Power budgets are a necessity these days. Due to increasing regulation, we’re seeing devices that must comply with efficiency limits in their power conversion (using a switching power supply or otherwise).

So what is a power budget? Much like a budget you might have for your personal finances, a power budget shows where all the possible power will be used by a device to by breaking it down into components and categories. In some situations, you might be told up front that you will have 3W available to run your design. However, sometimes as designers we start by calculating the total power a system needs and then taking actions such as replacing parts or redesigning circuits to cut back power to an acceptable level. So why might someone want to do a power budget from day one?

  1. Power availability — While you might have more power today, it doesn’t mean you’ll have it tomorrow. Designing a system for 3 W power consumption may be acceptable now, but designing a lower power system may meet future regulations. And the trends in the industry point in that direction.
  2. Battery Life — If your device is running off a battery, you likely do not have a choice whether you are doing a power budget. You want to maximize the life of your device on a single charge (assuming it is using rechargeable batteries) and your customers want the same. Just a few weeks ago I was complaining publicly on The Amp Hour about my new device with poor battery performance. Doing a power budget will point to the components consuming the most power so you can later optimize for longer battery life (hopefully this was a design constraint from the beginning).
  3. Heat generation — Heat is an unfortunate side effect of working with electronics. However,  it also has a 3 direct effects on your product and how it is used.
    1. User discomfort — No one likes having a hot laptop sitting in their lap. Nor a cell phone that is uncomfortable to hold.
    2. Circuit robustness — An often quoted specification of an op amp is the voltage offset drift. This sensitivity to temperature can have dire effects in systems that rely on analog accuracy. However temperature changes can create conditions that are unfavorable and could even cause device failure (such as thermal runaway). The heat of the whole system can end up affecting individual components as the nominal temperature inside your device rises.
    3. Product lifetime — The lifetime of a product can be drastically reduced by higher than normal temperatures inside the device. Extreme temperatures can begin to dry out capacitors and cause others to fail catastrophically. While it is possible for systems to fail in a drastic manner, the more likely outcome is a product that does not last for its specified lifetime. An example might be a TV that has a less vibrant LCD after 5 years due to excessive heat and component drift and fatigue. If the product was designed to have lower heat, the product would have lasted longer. For more on how to design and prevent early failures, check out Dave’s video blog about heatsink design.
  4. Cost (sizing) — More power means you need larger components. Other than the obvious requirement of needing more space (duh), it often correlates to higher cost components. Not only will you need larger packages for your components such as op amps and comparators in order to better dissipate heat. You’ll also need a larger power supply with more reliability. If a 5W and 20W power supply with 12V output are compared, the 5W supply has smaller magnetics and less wiring because there is less total current that needs to pass through.

So let’s look at an example power budget (click for a larger version):

As you can see, not much more is required than your datasheets and a spreadsheet type program. Even simpler is a piece of paper but I prefer the built in math functions of the spreadsheet program. The first two columns (A&B) are simply identifiers to allow you to recognize which components correspond to which set of data. The next two columns (C&D) determine the multiplicative factor. If you have 5 components that contain 4 op amps per, then that will consume 20x the power of a device that has the same supply current needs but only one op amp per and there is only one on the board.  The next two columns (E&F) show how much current each individual component contributes and then the sum of all the components of that type contribute. Note that this parameter on a data sheet would be listed as “supply current” or “active current”. The “quiescient” number is when the device is in a resting state and will likely be much less than the active number (and not relevant for this example). Finally, the supply voltage is listed (in column G) to calculate power (using the formula P=I*V) which is listed in column I per device. All of these contributors are summed, an efficiency is estimated (I assumed a poor efficiency linear type supply) and the total power required input to the device is given. Further calculations could result from much of this initial data.

I would be remiss without mentioning something about power budgets: you’re still going to guess about certain things. In fact it will be many different things. You might not have perfect data about your components. You might not completely trust the “typical spec” of one of your components. This is the point where you design in a margin of error. However, just like many other aspects of engineering, this is where tradeoffs come into play. You might want to design in 4 times more power capability than you calculate (to feel safe), but there are cost and spec requirements to consider. You will have to determine how confident you are in your design and how many resources you have available to your design. In the above example where the 5V parts require 408mA from the supply (~2W), I might over spec the part by designing in a part that is capable of supplying 600mA. The (50%) margin of error allows for future expansion (might need to solder in an extra part or two) and also gives a cushion if anything was miscalculated. In some situations this 50% might be too much (think a very low-cost, high volume design) or might be too little (think a military, high reliability design). It all depends on the situation and requirements.

Power budgets can be very powerful depending on the amount of time and effort you put into them. Otherwise they are educated guesses which may or may not be helpful to your project; how helpful they are might also depend on where you are in the design cycle. As stated before, these budgets are more and more of a necessity in a world more power conscious and with devices that continue to shrink. Your customers will expect longer battery life and your products to have yet more features. Teach yourself how to do power budgets now and it will pay dividends for you in the future.

[xyz_lbx_default_code]

Categories
Analog Electronics Learning

Homeschooling

I have lots of thoughts about education, especially higher education. The theme that keeps popping up in my head though is that school isn’t too far removed from teaching yourself. Honestly, let’s look at the learning process:

  1. Encounter a “problem” that needs to be solved.
  2. Do background research and look at past examples of how it was solved.
  3. Apply your newly gained knowledge to the problem at hand.
  4. If a new problem arises that is not encompassed by the recently acquired wisdom, go back to step 2.
  5. Report on your findings to others.

Doesn’t this sound like work? Or studying on your own? Or doing a hobby project? How is this any different?

Since I’ve had this debate with friends before I can tell you what others say. They say that the classroom environment and being shown some of the methods before doing the problem is helpful. That having the theory explained directly helps the brain to acquire the necessary knowledge. That being able to step into the professor or teacher’s office and ask a question is a nice luxury to have. But does this always happen? I know I’ve had teachers I don’t understand (or very much disliked), notes that didn’t make any sense upon second reading and semesters where I’ve taught myself completely out of a textbook (and of course it happened to be the worst textbook of all my classes that semester).

Furthermore, there are resources today that allow individuals to continue learning on their own. Video resources like MIT Open Course Ware (OCW) can replace or augment self learning on particular topics. Message boards can provide a forum to interface with experts and to keep up on recent developments in your industry. The prices of equipment have nosedived in the past 10-15 years, allowing many more people to have a “lab section” in their house. And things like hackerspaces allow for social interactions and places to flesh out more advanced ideas.

So what’s really left? Motivation. When you’re paying $30,000 a year or are spending every Tuesday and Thursday in a classroom somewhere, you’re going to make the most of your time there. You’re going to do the homework and go get the help you need to figure out the subject matter because you aren’t allowed to put it off a month or a year. You’re going to be motivated by the piece of paper you receive at the end of your degree program saying that you completed all of the necessary requirements and did so while meeting or exceeding the expectations of your institution. Or you might even want to just prove you can do it. All of them really are valid reasons, they just don’t exist when you’re teaching yourself at home. External motivation is needed for many people (myself included) to pick up a book on a subject. In fact “motivation, momentary lapse of” is how this post came about. I was reading about active filters for a side project (where the motivation is showing off the side project and becoming “internet famous”) and I started thinking about how similar my current situation is to my former schooling. And all of the self-teaching and gained experiences are occurring without paying the $31,000 a year (yes, you read that right, tuition went up just since the last time I listed the number).

Do I hate higher education? No, I think there are some factors that make it invaluable to those that pursue it (and many more that benefit from the output). I may still try to get back to grad school myself some day. I love that there are institutions dedicated to research that might never get done otherwise. I’m glad that there are institutions that stress the rigor of the scientific method. I love that there are places where learning and advancing knowledge is the main purpose and task of those that attend. But all I’m saying is sometimes this happens in basements and bedrooms too.

Is learning at home without the structure of schools possible, especially in higher education? Does anyone ever teach themselves at home and why do you do it? What problems do you have with it? People currently enrolled in a University, do you find any fault with this thought?

Categories
Analog Electronics Learning

They Don’t Make ‘Em Like They Used To!

Being an analog engineer, I’m around “more experienced” engineers on a daily basis. However, a group of younger engineers often find ourselves acting much older than we are, shouting things like “Get off my lawn!” and “Back in my day…” (really, we had a whole list).

Anyway, another common one that comes up is “They don’t make ’em like they used to!”.  Do we as engineers know WHY they don’t make them that way anymore? Of course we do. The lower reliability and requirements for many more people to assemble the devices honestly doesn’t make sense these days. With lower priced labor the world over and low tolerance for waste and inefficient processes, I know I wouldn’t make the proverbial “them” that way anymore. It just doesn’t make sense.

But why am I mentioning this? In episode 12 of The Amp Hour, Dave Jones and I were discussing the Tektronix scope that I currently have disassembled and am attempting to piece back together in working order.  It’s the 485M, the military version of the very popular scope.  Right now I’m looking at getting the power supply back on its feet, the voltages were woefully low. More on that in later posts hopefully. For now, let’s concentrate on looking at the awesome design tactics and fabrications inside an old scope.

Note: I am a pretty bad photographer, please excuse any non-professional looking images.

A view of the quite complex button schema of old Tek scopes. Each button controls an individual switch, pot or selector switch. And yet it has many of the features of modern scopes match these exactly.

I LOVE modular design and this is a great example. If a technician (a Tek Tech?) found that a module wasn’t performing correctly this entire module could be switched out to check to see if it is indeed this module.

A closer view of the module. Of note is the resistor jumpered directly across the signal lines of the end connector. Perhaps this is a later fix for a customer issue. It’s also a good view of a mechanical connector that reaches all the way back from the front of the module. It’s a compound switch, pulling on it activates the arm in one direction and pushing on it does some other completely different action.

A close up view of the modular connector. I also like seeing the layout patterns done by hand before CAD programs were prevalent. Interesting to see where they flooded the ground planes.

A closer view of the analog components on one of the modules. Notice this was mainly resistors and a smattering of socketed op amps.

Another view of a mechanical arm reaching all the way to the back of the chassis. Likely a custom part as discussed on The Amp Hour.

This selector switch was the main voltage range switching. It had a compound action as well (inside was a fine tuning I believe) whereas the outside switch was the larger 1-2-5 multiple decade switching.

And finally, a view from the top. Note the >7 kV warning on the CRT tube. No touch!

So there it is, as Dave calls it, “nerd porn”. Isn’t it interesting to see how instruments were constructed not too long ago? It sure was more labor intensive and likely much more expensive than you can pick one up today on ebay. The benefit is that the hand-made and through-hole nature of this board makes it ripe for fixing AND without straining my fragile old eyes. Dangnabbit!

Categories
Engineering Work

Recruiting In An Emerging Age Of Makers

I’ve started reading resumes from the bottom up.

What does this mean? It means I’m looking for passion. It means I’m looking for interest. It means I look for people who do electronics for fun. It means that classroom experience–while important–is not getting you the job. In fact, quite the opposite. If you’re spending all of your time in the classroom, how useful are you? Yes, understanding the basics are important. But if you’re going to quote me an equation you learned instead of going out and soldering and desoldering components to a board, how will I know that you’re a legit worker that is willing to get their hands dirty? (solder-y?)

Thanks to the global economy, no job is secure anymore. OK, we can handle that. But in an increasingly independent work force, we’ll see more contract work and less (yes, even less than current levels) loyalty to corporations. As such, the recruiting (and hopeful retention) of talent will become one of the most important jobs. Innovation will now be negotiated for and fought for instead of attempting to induce it in a laboratory setting. The risk takers will be encouraged to continue to take risks once they are plucked from their garages and basements.

I believe hackerspaces will be the new recruiting grounds. We’ve already seen people that are targeting them for sales (chips, discretes, software) because the projects that are made often are spectacular advertisement; the open source hardware people develop in these collaborative workspaces often become platforms to seed many other projects as well. In the future, we’ll also see recruiters hanging around hackerspaces looking to pluck talent before the person realizes they’re not just working on an Arduino for fun, they also have a future as an embedded system. You just wait, it’ll happen. For at least one person interviewing potential candidates, it already is.

Categories
Blogging Conferences OSHW

I’m at the Open Hardware Summit!

I’m spending the day at the New York Hall of Science. It’s amazing. The venue is perfect. The swag from the OHS people and sponsors is so cool. I’m completely smitten with everyone here. I’m kind of reverting to a childhood state I’m so excited.

Why?

Well, because this feels like the beginning of something much much bigger than me and that I get to watch it unfold in front of me. And participate, that’s key as well. And since I looked for a while for people online and failed and new get to sit in a room with 200 people that do hardware, it gets me excited. These are my people. My nerdy, awesome people.

Don’t get me wrong, open source hardware has been going on for a while. This is not new. But this is getting bigger and from chaos we are seeing order emerge. The open source hardware standard will be worked on and released at the end of this conference. You can view the 0.3 version on the Open Hardware Summit page.

I’m writing this mid-way through the day. We’ve already heard from Limor Fried from Adafruit and Gerald Coley from BeagleBoard. I can’t wait to hear more and hope to post them all here soon.

Categories
Blogging Digital Electronics

I’m on EETimes!

So I’ve been at ESC Boston since Monday, both as a participant and as a writer. It’s been a really cool experience meeting a lot of people in the technical writing field and a lot in the publishing industry (as well as those in the technical side of things, of course). And today for the first time, I was published in EETimes on the EELife section. Check out a couple of my articles, linked below.

Any comments can be left here or on the specific article pages.

Categories
Blogging Conferences

A September Update

So it’s quite apparent I haven’t been around posting too much. The date on the last post makes that pretty obvious. I have been doing some fun and exciting things though!

First off is The Amp Hour, a new electronics podcast/radio show. We just completed our 8th episode yesterday and it seems to be going well! We were very lucky to have much of Dave Jones’ wonderful community at EEVblog make the jump over and listen to us. It’s nice to have a strong base of listeners to start with and we appreciate everyone of them (I appreciate you doubly if you happen to read here as well!).

Next, I’ve been reworking my electronics lab at home, building up my gear holdings and working on some new projects. It’s been really fun, if not time consuming. All of the time that used to go towards bugging you with blog updates seems to be eaten by that activity. I know there will be lulls in the future, so I’ll try to blast out some ideas I’ve had rattling in my head when that happens. I’m really interested in a topic we discussed on The Amp Hour known as “The Creative Economy”. Basically the idea that so much equipment has become such a commodity that the only true value to add to products and services will now be based on how creative you are. It’s already started and it will only become more apparent.

And lastly, on the same note as above, I’ll be attending the Open Hardware Summit coming up in NYC. It’s right before the Maker Faire (which I won’t be able to attend unfortunately) and should give me and everyone reading this even better insight into the thing fueling much of the creative economy: open source hardware. The few days prior to OHS, I’ll be at ESC Boston doing some freelance work for EEtimes (on their EELife blog section). I’m looking forward to that as well. It was a direct result of going to the ESC in Chicago, which I’ve written about on here a few times.

So that’s it for now. Talking, doing and writing. That is my life. And I enjoy it. And I hope to share more of it with you soon, so please hang on.

Categories
Podcast

Shhh, Don’t Tell The Aussie…

I know we said we wouldn’t talk about it on our sites any more, but I figured once more can’t hurt. We have our latest episode of The Amp Hour up on the new website, just waiting to be downloaded or streamed.

I will say though that you should pull the RSS feed ASAP in order to not miss any future radio shows. Who knows what kind of hijinks you’d miss out on?

Anyway, don’t tell the Aussie! I don’t want to upset my co-host. But do remember to shoot over to The Amp Hour for the 4th installment of the new radio show and leave some nice comments there.