Every Electronic Design Automation (EDA) tool is a bit different. Some have more features than others, some have different features, some offer simulation, some don’t. But they all have a few features in common: they allow designers to capture a schematic and layout a PCB.
In a schematic diagram, components are represented as abstract symbols.
Basic EDA Structure
There are four basic parts of every EDA tool. The pattern editor, component editor, schematic layout, and PCB layout program. The names of the modules might vary from program to program, and they might be used differently, but they all exist in one form or another.
- Component editors alter the appearance of schematic symbols.
- Pattern editors alter the appearance of land patterns.
- Libraries hold collections of linked components and patterns for reuse from design to design.
- Schematic Layout arranges the connections between components.
- PCB Layout arranges the patterns and the traces that connect them.
To make things even more exciting/confusing, the land patterns associated with those pads are often incorrectly called footprints by engineers, even though the metalized lands have to be larger than the metalized pads/pins they mate with. Electronics Engineering is terrifically confusing to begin with, the situation is not improved by engineers that use the same words to describe two different things. But that’s the world we live in, so let’s try to make sense of it.
- Discrete components have metalized pads or pins on their base and sides.
- Printed circuit boards have metalized lands on their outer layers.
A discrete component’s metalized pad pattern and a printed circuit board’s land pattern are identical in layout and centerline spacing, but the metalized lands are always bigger than the metalized pads.
The size and shape of footprints and lands has been largely standardized into IPC-7351, a document that describes the pin pattern, layout, and naming convention for all standard parts. The document is unfortunately locked behind a paywall. That’s okay, it’s not a very exciting read, and most EDA programs have incorporated the data from the document into their pattern editor libraries. “Wizards” generate the pattern and pattern names needed in the program. Additional patterns can be constructed manually from information supplied in datasheets.
The abstract symbols that represent PCB components are created and edited in a component editor. Components are shapes that abstractly define the function of a physical part, with pins that represent metalized pads/pins on physical components. There are two standards in broad use and as long as the symbols don’t jump from one standard to another within a schematic document, it’s usually pretty easy to keep track of what is going on.
When you pull a component from the library, you should do two things.
- Make sure the part is available. It’s very common for EDA part libraries to be out of date and include parts that are now obsolete and unobtainable.
- Double-check the land pattern that is associated with the part number is correct. You never know who made the library entry, and it’s possible that they read the datasheet incorrectly or they copied the footprint in a 1:1 manner.
Electronics design and layout is a complicated activity. So engineers often take shortcuts where they can find them. It’s quite common for a designer to have a “grab-bag” of sub-circuits that, once proven successful, they will reuse from design to design. There’s no need to redesign everything from scratch every time.
At the beginning of the course, Bob and I had a phone call where we talked about what design elements we wanted to include in the badge (IMU – Yes, Neopixel – Yes, Wireless – No, etc…). Then we drew a block diagram. At that point, Bob started designing each of the blocks as a separate circuit.
While you have been layout out your schematic, your EDA has been quietly been keeping track of your land patterns, and the connections between the pins. If it’s been set up properly, there’s a good chance that it knows which pins require special routing rules as well.
But when you first convert it, you usually get an explosion of parts onto a blank page connected with a flurry of ratlines.
At that point, it’s usually a good idea to remove the ratlines from view and organize the parts by circuit block.
At that point, you can start positioning the parts on the PCB and running traces to connect them.