Re: How do you design a circuit?



On 2 Jun 2006 05:32:40 -0700, in message
<1149251560.070285.287610@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "ku7485"
<ku7485@xxxxxxxxx> scribed:

This might be a dumb question to some. I've been reading a lot about
electronics, but never find a good piece of text that properly tells
about how to design a PRACTICAL circuit. I've seen some basic examples
such as connecting a LED, resistor, and a battery and using Ohm's Law
to determine to right resistance, but that's about it. I never have
heard why an engineer explain how they built their own circuits and why
they chose these parts. We'll anyway, I'm just wondering how people
are able to design.

It's a better question than you think. A lot of people get engineering
degrees, every year. They really don't teach design in college, though.
They give you some of the tools you will employ. To design requires
mentoring and knowledge of the system that you will be designing for.

I've seen a group of graduates with no real experience, outside some
software testing, try to design a complex, integrated automatic test
equipment test station. They relied on *one* experienced engineer for
guidance, and soon abandoned his guidance because he was telling them
things they didn't want to hear. The project was a dismal failure.

On the other hand, with an infrastructure set up with a solid
plan-design-build scheme laid out, with different and experienced engineers
at each stage, with reliance on knowledge of the system being built for,
some extraordinarily complex projects can be completed in short order, with
all the parts melding smoothly into place with apparently little effort.
The effort is put forth in careful planning up front and execution of the
plan without undue variance. A good team makes hard work look easy.

Choosing parts is some of the most difficult work. It takes a lot of study
of requirements and specifications, dedication and attention to detail.
Part of the reason the "dismal failure" I mentioned previously went so
badly, is that the inexperienced engineering team spent little if any time
studying the specifications of the equipment, layout and wiring of the
system they were replacing. Thus, much of what ended up being purchased
did not make a good fit with the existing equipment. They were arrogant.
They thought they could make up for hardware mis-matches by making
short-cuts in the software. They were wrong.

.



Relevant Pages

  • Re: Slowing TL acquisition while allowing interstellar scope
    ... An Operator of equipment does not necessarily have to know how the equipment does what it does, just that pressing buttons, throwing levers, or otherwise manipulating what ever human interface there is will accomplish said task. ... A repair person does not necessarily have to know all of the design functions, nor be skilled in operation OTHER than being able to operate the equipment sufficiently to assess the point of failure, and after maintenance, whether or not the equipment is operating within performance spec. ... The design engineer, on the other hand, must be able to evaluate whether or not the equipment in the design process will meet the performance spec - which means that he MUST be able foresee and understand the operational parameters, possible points of failure, and required maintenance. ...
    (rec.games.frp.gurps)
  • Staff HW Engineer ~ Lead Us to ATCA & Beyond in Your End-to-End Board-Level HW Desig
    ... The senior level hardware engineer looking for the product realization ... and true ownership that comes with full end-to-end board-level hardware ... help us retain dominance in the design of high performance switching ...
    (comp.arch.embedded)
  • Re: Another proposal
    ... alleged DipEng does nothing for me. ... piece of equipment which had been designed by a DipEng. ... I then asked if I could speak to the engineer, ... could explain to him how he made his fundamental design error. ...
    (rec.audio.tubes)
  • Re: Slowing TL acquisition while allowing interstellar scope
    ... An Operator of equipment does not necessarily have to know how the equipment does what it does, just that pressing buttons, throwing levers, or otherwise manipulating what ever human interface there is will accomplish said task. ... A repair person does not necessarily have to know all of the design functions, nor be skilled in operation OTHER than being able to operate the equipment sufficiently to assess the point of failure, and after maintenance, whether or not the equipment is operating within performance spec. ... The design engineer, on the other hand, must be able to evaluate whether or not the equipment in the design process will meet the performance spec - which means that he MUST be able foresee and understand the operational parameters, possible points of failure, and required maintenance. ...
    (rec.games.frp.gurps)
  • Re: A Challenge for Stewart Pinkerton
    ... amplifier design, ... actually a tube group, and you are a very clever engineer, I challenge you ... But, Ivy, my old darling, we don't *need* a favour. ...
    (rec.audio.tubes)

Quantcast