What is Hardware Design Vs PCB Design?

⚡Many engineers, startup founders don’t understand clearly what is Hardware Design, they don’t see any difference between Hardware design and PCB Design.

They ask questions like “can you design PCB for my battery-based sensor or BMS or data logger?”

What they really mean is “can you design hardware for my product with XYZ functionality?”

I get these kinds of inquiries on daily basis.

What is Hardware Design Vs PCB Design? 1

Let me try to explain:

What is Hardware Designing?

Hardware design is the stage where the engineer or a team selects various components to develop a functionality and figures out the circuit for each and every block which is required in the product and does a rough BOM cost analysis so that it meets the target manufacturing cost.

This is the code hardware design.

For this stage to be effective you need to have a technical specification document that details what is needed on a board or in a product.

What is Schematic Capture?

After the hardware is frozen in the previous stage, you need to create a schematic using an EDA tool, like Altium® Designer (in my case), KiCAD, Eagle, ORCAD, etc.

This is nothing but a digital form of the circuit with which you can create the PCB design. This stage has 3 parts:

  • Schematic symbol creation
  • Creating the circuit
  • Optimization/reviews.

What is PCB Designing

In this stage, you design the PCB, basically how each IC, component will be connected on the PCB using the tracks, in its physical form.

This stage has 4 parts:- footprint creation

  • Component placement
  • PCB layout, in some of the complex designs you need one more stage of EMI/SI analysis to reduce the iterations
  • and reviews.

Actually, schematic capture and PCB designing is also part of over all hardware design only.

Above is just on high level, hope it was easy to understand and helps some of you.

Another thing which is quite challenging for less experience people in the hardware development is how the whole hardware development works.

They think, you design the hardware, prototype it, test it and it should work, 1st time right, yes, every wants this.

But, first-time-right design is a myth, you can only reduce the probability of errors by various levels of reviews and a detailed checklist.

If the product you are designing has nothing new and everything (IC, MCU) you are using is used previously in some of your other projects and you have previous experience, then yes probability of 1st time right design is quite high.

but still, there will be a chance of error.

Not many people will agree to this as they are scared to tell the truth.

This hurts their ego or fame when they accept that their design will have chances of errors in 1st prototype.

This is what I learned hard way

  • be upfront
  • set expectations right
  • and reduce stress, both sides 🙂

Read this, if you are interested to understand what are the the steps involved in a typical hardware development.

I hope you found this information useful. If you have any feedback, you can share in the comments section or you can also contact me directly.

Read more interesting articles on Embedded Systems Design.

If you need help on custom embedded hardware development or design optimization, do reach out to me. I will be happy to work for your product development.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.