PCB Design Fundamentals: Prototyping and the PCB Design Flow

Publish Date: May 10, 2018 | 20 Ratings | 3.80 out of 5 | Print

Overview

This article explains the importance of prototyping and product development in the PCB design flow. After explaining the difference between the two stages, it goes on to describe various tools that are best fitted to each stage of the design flow. The National Instruments PCB Design Fundamentals Series is your free resource on the Internet for learning about prototyping Printed Circuit Boards (PCBs). This selection of resources includes an introduction to terminology, design best-practices and additional such as prototype fabrication.

The series is divided among a number of in-depth detailed articles that offer HOW TO information on the important concepts and details of PCB Design.

Click here to return back to the PCB Design Fundamentals page.

Table of Contents

  1. Introduction
  2. Why Prototype?
  3. PCB Design Flow - Step 1 - Part Research & Selection
  4. PCB Design Flow - Step 2 - Schematic Capture
  5. PCB Design Flow - Step 2b - Simulation
  6. PCB Design Flow - Step 3 - Board Layout
  7. PCB Design Flow - Step 4 - Verification & Validation

1. Introduction

Though the PCB design flow can be split a number of ways, it is best to think of it as having two fundamental stages: Prototyping and Product Development.

Prototyping occurs at the earliest stage of design and involves individual engineers researching how to define a certain system or application. The experimental nature of this stage is fundamental in being able to develop hardware that can meet specifications. When the design has been validated, it can be passed onto the latter stages of the design flow (i.e. product development). The ultimate goal of the prototyping stage is to have a successful product that is accurate, efficient and meets specifications. You want to accomplish this with as few prototype iterations as possible to maximize time and resources.

Product Development is about making a PCB ready for a final application. The prototype has already met the design specifications (filtering, amplification, acquisition, measurement etc…) and it is now ready to take that design and to implement it using the best practices in design. Most companies have individuals that are layout experts, and are involved in product development. During this design stage, you are developing for manufacturing and as such are concerned about increasing product yields and decreasing manufacturing re-spins.

Figure 1 - Complete Design Flow

 

It is important to understand this difference as there are various tools that are best fitted to each of these stages of the design flow. Although for product development board layout specialists are available, the researcher is generally a domain expert. A domain expert needs to be able to quickly design, without being an expert in schematic capture, simulation or layout.

For example, for prototyping you need to be able to:

  1. Define a circuit schematic quickly
  2. You need to validate circuit behavior with advanced analysis techniques
  3. Transfer a schematic to layout easily
  4. Validate the behavior of the design accurately

For the PCB Design fundamentals we will focus on the prototyping stage and help you (the individual designer) to learn more about developing a PCB prototype.

We can split the prototyping stage pictured above (Design > Prototype > Validate) into four steps: Part Research and Selection, Schematic Capture and Simulation, Board Layout, and Verification and Validation.

Figure 2 - Design Flow

 

 

Back to Top

2. Why Prototype?

There are six main reasons to prototype:

  1. Fail early and inexpensively:  Real innovation always includes a risk of failure. By building a prototype, you can quickly weed out the approaches that don’t work to focus on the ones that do.
  2. Gather more accurate requirements:  Almost half of all project costs are attributed to rework due to inadequate requirements. By developing a working prototype, you can demonstrate the functionality to help solidify requirements for the final design.
  3. Technically understand the problem:  By developing a functional prototype, you can address both the foreseen and the unforeseen technical challenges of a device’s design. You can then apply those solutions to a more elegant system design when you move to the final deployed solution.
  4. Resolve conflicts:  By taking advantage of a prototyping platform, you can quickly conduct several different implementations of the feature and benchmark the resulting performance to analyze the trade-offs of each approach. This can save time, but it also ensures that you make the correct design decisions.
  5. Rally financial support:  By developing a prototype to demonstrate the feasibility of your idea, you lower the risk of investment and therefore increase the probability that your idea will be funded.
  6. File patents more easily:  Though no longer required, a prototype is still the best and safest way to demonstrate “reduction to practice.” Furthermore, key components of a patent application, such as patent drawings and the inventor’s logbook, can be developed through the prototyping process.

 

Back to Top

3. PCB Design Flow - Step 1 - Part Research & Selection

Before even designing, the engineer needs to be able to select components that will make a circuit function. There are a number of semiconductor manufacturers including Analog Devices, National Semiconductor, NXP, Rohm, Linear Tech, On Semi and Texas Instruments, that create devices that meet varying specifications. There are a number of ways for engineers to research parts including:

  1. Datasheets on semiconductor performance (many can be found at datasheetcatalog.com
  2. Manufacturer web content; Analog Devices makes a number of their products available for evaluation through their Evaluation Hardware & Software page.
  3. Simulation tools that can be downloaded and used to evaluate components from that manufacturer.

 

 

Back to Top

4. PCB Design Flow - Step 2 - Schematic Capture

Schematic capture involves taking symbolic representations of components (resistors, capacitors, amplifiers, comparators etc…) and wiring them together into a visual diagram which can be easily viewed to understand the functionality of the circuit. The purpose of the schematic is to view the building blocks of the circuit from a theoretical perspective.

The schematic consists of component symbols and wires (also called nets).

Figure 3 - Schematic Design

 

 

Back to Top

5. PCB Design Flow - Step 2b - Simulation

SPICE Simulation is the industry standard in simulation of circuit components. Simulation can be used to evaluate the behavior of real world components in a virtual environment, thereby allowing you to do advanced analysis of a design earlier in the design flow. By visualizing the behavior of the circuit at the earliest stage of prototyping, one can reduce errors and improve performance. Engineers often build the schematic of their design, and then simulate and visualize its characteristics.

Along with SPICE there are other languages and parameters which simulate circuits, including PSpice and HSpice.

To learn more about simulation view the SPICE Simulation Fundamentals

 

 

 

Back to Top

6. PCB Design Flow - Step 3 - Board Layout

A schematic when completed is transferred to board layout. Each symbol in a schematic is associated with a landpattern. A landpattern visually represents the physical dimensions of an IC or semiconductor package. The landpattern translates the symbol of a component (such as an Operational Amplifier) to an 8 pin rectangular package. During the board layout stage the design is defined as it will eventually look when prototyped. This means defining the board outline, placing parts, creating connections between parts in copper, and then finally exporting for fabrication.

 

Figure 4 - Board Layout

 

 

 

Back to Top

7. PCB Design Flow - Step 4 - Verification & Validation

Once the board is fabricated, the engineer needs to validate the behavior of the prototype. Once it is validated, it can be handed off to product development and be prepared for manufacturing. Validation requires taking measurements from the board and ensuring that real performance meets the simulated performance (or specifications).

Figure 5 - Final Design

 

 

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit