Common mistakes in PCB schematics include power pins tied to the wrong rail, incorrect component values on IC configuration pins, discrete semiconductors chosen on DC ratings alone, misassigned digital interface pins, unintended net connections and poorly matched circuit protection.
These errors can pass a basic electrical rules check (ERC), depending on the tool and configured checks, because the drawing itself is valid.
Catching them means comparing every connection and value with the component datasheet and the intended circuit behavior.
Each example below is an annotated schematic, from a GNSS module powered from a 5V rail to a USB port protected by the wrong TVS (transient voltage suppressor) diode.
For each mistake, you will see what goes wrong, why ERC misses it and which datasheet information resolves it.
Why Do Schematic Errors Pass the Electrical Rules Check?
Schematic errors can pass a basic ERC because the check confirms that pin types may legally connect, not that a connection is electrically correct for the parts involved.
An ERC works from the electrical type assigned to each symbol pin, such as input, output, power or passive, and flags conflicts such as two outputs driving one net or an unconnected input.
According to the KiCad Schematic Editor documentation, ERC also reports power input pins that are not driven by a power output and conflicting labels on the same net.
It has no knowledge of a device’s supply limits, a regulator’s reference voltage or a diode’s reverse recovery time.
Unless the checker has voltage-limit rules for that part, a 5V rail connected to a power pin rated for 3.6V maximum is a valid power-to-power connection as far as the ERC is concerned.
Many schematic errors involve connections that look reasonable until you compare them with the component datasheet or reference design.
Other errors come from a simple mismatch between a component’s specifications and its electrical function in the circuit.
Finding either type requires information about how the circuit is supposed to operate, and each of them can result in complete product failure.
The six error categories below are where that gap commonly appears, along with the information needed to catch each one before PCB layout.
What Are the Common Mistakes in PCB Schematics?
Six common functional mistakes in PCB schematics are power supply connection errors, incorrect component values on IC pins, discrete semiconductor selection errors, digital interface connection errors, net connectivity errors and circuit protection selection errors.
Each one can survive a basic ERC because the schematic is drawn correctly, even though the circuit will not work as intended.
Each one also needs a specific piece of information, usually from the datasheet, application note or reference design, to catch it.
Is Every Power Pin Connected to the Right Voltage Rail?
A power supply connection error happens when a supply pin is tied to a rail outside the device’s rated range, or when pins that need different voltages share one rail.
Power connections are a good place to start a review because one incorrect rail can affect several devices at once.
In the example below, a u-blox NEO-M8N GNSS receiver has both VCC and V_BCKP connected to a 5V rail.
The u-blox NEO-M8 data sheet lists an operating range of 2.7V to 3.6V for VCC and an absolute maximum rating of 3.6V for both VCC and V_BCKP.
Both pins are connected, so finding this error requires comparing the rail voltage with the device’s supply limits, which an ERC cannot do.
The same figure flags supply pins left floating, and the pin descriptions in the datasheet state how each unused supply pin must be handled.
To prevent these problems, check each supply connection against the pin descriptions and the recommended application circuit, details that are easy to overlook in a long datasheet.
Do Connected Devices Share Compatible Logic Levels?
Devices that share a bus need compatible logic levels on both their core voltage rails and their I/O supply rails.
According to the TI voltage-level-translation application report (SCEA021A), the driver’s high-level output voltage (VOH) must be greater than or equal to the receiver’s high-level input voltage (VIH) to establish a valid logic high.
The same report gives the matching condition for a logic low: the driver’s low-level output voltage (VOL) must be equal to or less than the receiver’s low-level input voltage (VIL).
Check the receiver’s own datasheet for input voltage tolerance as well.
The same report shows why this matters: a 3.3V LVTTL output has a VOH of 2.4V, while a 5V CMOS input needs a VIH of 3.5V, so a standard 3.3V device cannot drive that input directly.
A 1.8V I/O bank driving a 3.3V peripheral without a level shifter is a potential mismatch of the same kind, and the specific VOH and VIH values decide whether it works.
Decoupling requirements belong in the same review, particularly where the manufacturer specifies capacitance for an individual pin or a group of supply pins.
Are the Component Values on IC Pins Correct?
An incorrect component value on an IC configuration pin changes how the circuit behaves without breaking any ERC rule, because the resistor or capacitor is still correctly connected.
Many ICs require external components to set their operating characteristics, and the values are sometimes buried deep in the datasheet.
In a DC/DC converter controller, for example, a feedback divider sets the output voltage, while passives on the COMP or FREQ pins set loop stability or switching frequency.
An incorrect value can stop the circuit from operating correctly even though it passes every basic ERC.
Component values need to be checked against the intended circuit behavior using the datasheet equations, tables or graphs.
In the feedback network shown, the review identified two problems: a feedback voltage below the target reference and an oversized series resistor.
Recalculating the feedback voltage and checking the resistor against the application circuit gives the reviewer a clear basis for correcting both values.
Datasheets also set limits on the resistor values themselves.
The TPS54340 datasheet, for example, states that the feedback network should carry more than about 1 µA because of the FB pin input current, and notes that higher resistor values can cause noise immunity problems.
Does the Discrete Semiconductor Suit the Circuit Function?
A discrete semiconductor selection error happens when a part meets the circuit’s voltage and current ratings but fails on the specification that actually governs the circuit, such as reverse recovery time or terminal capacitance.
Many well-known general-purpose discrete semiconductors still see widespread use across many applications.
A good example is the 1N4148, a fast-switching through-hole diode used in many moderate-speed, moderate-power circuits.
The Vishay 1N4148 datasheet rates it at 100V repetitive peak reverse voltage and 150 mA average forward current, with maximum reverse recovery times of 4 ns and 8 ns under two different test conditions.
More advanced applications place greater demands on specific parameters, because those parameters largely govern electrical function and reliability.
MOSFETs in fast switching circuits, for example, are limited by their terminal capacitances, while voltage and current ratings may be secondary.
The TI gate driver fundamentals report (SLUA618A) explains that switching performance is set by how quickly the device voltages can change, and that the length of each switching interval is a function of the parasitic capacitances.
From a design review perspective, it helps to annotate the schematic sheet so that the upper or lower limit on each critical specification sits next to the component’s symbol.
That note tells the reviewer and the purchasing team which parameter cannot change when a substitute part is proposed.
Are Digital Interface Pins Assigned and Connected Correctly?
Digital interface errors most often appear where signals cross between devices, such as reversed differential pair polarity on an interface that requires fixed polarity, a UART TX pin connected to the other device’s TX instead of RX, and clock signals connected to pins that cannot accept a clock.
These problems become easier to miss on processors with large pin counts.
In programmable logic, particularly large FPGAs (field-programmable gate arrays), clock and data lines are easy to transpose or assign to the wrong pins without careful reading of the datasheet and reference design material.
To verify an interface, compare each connection with the pin capabilities and interface requirements at both devices, not just at the processor.
Check that each interface also has the termination, coupling and pull-up components its specification requires.
Reviewing pin assignments on a large processor can be time-consuming, but reference material and vendor engineering support can help identify incorrect assignments before layout.
Does the Netlist Match the Intended Connections?
Net connectivity errors are unintended shorts or open connections created by missing labels, accidental junctions, misplaced no-connect markers or reused net names, and they change the circuit without making the drawing look obviously wrong.
Reusing a net name can join connections that were meant to remain separate.
In KiCad, a no-connect flag tells the ERC that a pin is intentionally unconnected, so a flag placed on a pin that should be wired hides the missing connection instead of reporting it.
Whether that connection is correct depends on the schematic hierarchy and the scope of the net label, since a global label and a sheet-local label behave differently.
The compiled netlist shows how the schematic tool resolved connectivity, so it is the record to check rather than the drawing.
The synchronized PCB and its routing still need their own verification once layout begins.
How Should Current-Sense Connections Be Drawn?
Current-sense connections should be drawn so that the sense inputs measure directly across the shunt and the sense-return path survives the move into layout.
The TI INA225 datasheet recommends connecting the amplifier inputs to the sensing resistor with a Kelvin, or 4-wire, connection, because trace resistance adds measurement error when shunt values are low.
Separate sense and power-return nets can be joined at a defined location with a net tie.
This lets the designer control where the nets connect while keeping separate net names for routing.
Is the Circuit Protection Matched to the Interface It Protects?
A circuit protection selection error happens when a TVS diode, fuse or gas discharge tube is chosen on a single rating, usually voltage, instead of being matched to the expected disturbance and the limits of the circuit it protects.
A TVS diode needs a suitable working voltage and clamping response, and a protection device on a high-speed interface also needs low enough capacitance.
The ROHM TVS diode selection application note recommends choosing a reverse working voltage (VRWM) higher than the voltage on the line and a clamping voltage as low as possible for that VRWM.
Excessive capacitance from a generic TVS chosen on voltage alone can degrade signal integrity on a high-speed line.
On USB 2.0 D+ and D- lines, choose a low-capacitance ESD device, account for the loading added by the connector and PCB, and verify the assembled port against the USB 2.0 high-speed signal-integrity requirements.
The TI ESD321, for example, has a typical I/O capacitance of 0.9 pF and is listed by TI as suitable for protecting USB 2.0 interfaces.
Does a Bidirectional Data Line Need a Bidirectional TVS?
Data flowing in both directions does not, by itself, require a bidirectional TVS.
The choice depends on the signal’s voltage polarity: the ROHM application note explains that a unidirectional TVS suits signals that stay positive relative to ground, while signals that swing positive and negative need a bidirectional device.
Datasheets and application notes provide this selection guidance, and the result must then be checked against the product’s test requirements.
Fuses and gas discharge tubes need the same application-specific review of their ratings and protection roles.
What Should a Schematic Review Checklist Include Before Layout?
A schematic review checklist before layout should cover power connections, external component values, semiconductor selection, digital interfaces, net connectivity and circuit protection, and should pair each one with the information needed to verify it.
The table below connects each review stage with the error it catches and the information required to resolve it.
| Review stage | Potential error | Information needed |
|---|---|---|
| Power connections | Wrong rail, floating supply pin or incompatible I/O voltage | Supply limits, pin descriptions and logic thresholds |
| External component values | Incorrect voltage, frequency or timing | Datasheet equations, tables and application circuits |
| Semiconductor selection | Adequate DC ratings but unsuitable switching behavior | Circuit function, switching conditions and device characteristics |
| Digital interfaces | Wrong pin assignment or missing interface components | Pin capabilities and termination or coupling requirements |
| Net connectivity | Unintended short, open connection or incorrect sense return | Compiled connectivity, label scope and intended connection points |
| Circuit protection | Excessive clamping voltage or interface loading | Protected-device limits, protection characteristics and test conditions |
The common thread is that every row depends on information the ERC does not have.
A reviewer who works through the table sheet by sheet, with the relevant datasheet open, can catch these errors before placement begins.
The last column also shows where automated tools can help, provided they have access to the same device information.
How Do Industry Requirements Change the Schematic Review?
Industry requirements add two checks to the schematic review: whether each component carries the required qualification, and whether the protection circuit survives the disturbance levels the product will be tested to.
In automotive designs, discrete semiconductors are typically specified to AEC-Q101, a failure-mechanism-based stress test qualification for discrete semiconductors in automotive applications.
Where the program requires AEC-Q101 parts, a commercial-grade MOSFET or diode in an automotive module is a selection error even when every electrical value is correct.
Approval for a specific application is a separate decision, so check the approved-part requirements for the program as well.
For ESD protection, IEC 61000-4-2 defines the test levels, with Level 4 set at ±8 kV contact discharge and ±15 kV air discharge, as listed in TI application report SLVA957A.
Medical devices tested to the 4th edition of IEC 60601-1-2 face ESD test levels of ±8 kV contact and ±15 kV air, up from ±6 kV contact and ±8 kV air in the 3rd edition.
Knowing the test level before the review lets the reviewer check each TVS diode’s ESD rating and clamping performance against the actual stress it must survive.
The TVS rating is only one input, because PCB layout and the assembled equipment also determine system-level immunity.
When Is the Best Time to Catch Schematic Errors?
The best time to catch schematic errors is before PCB layout, because corrections made then do not undo any placement or routing work built on a faulty circuit.
Once layout starts, a wrong rail or a mis-assigned FPGA pin can force changes to component placement and routing.
After fabrication, the same error can require a board re-spin, depending on the fault and the rework options available.
Automated checks can reduce the time spent finding these errors, provided the tool has the necessary device information and circuit requirements.
A human reviewer still needs to resolve assumptions about operating conditions and intended connections, so automated analysis works best as a first pass that gives the engineer a shorter, better-targeted list to review.
Ready to Catch Schematic Errors Before Layout?
The common mistakes in PCB schematics covered here, from a 5V rail on a 3.6V GNSS module to a generic TVS on a USB line, all pass ERC and all become visible once the schematic is checked against the datasheet.
As an agentic schematic analysis platform, CADY reviews your netlist and BOM (bill of materials) against component datasheets and more than 1,000 design rules to flag voltage mapping, connection integrity and communication protocol errors before your board moves into PCB layout.
Upload your netlist and BOM, run the analysis, and review the flagged errors and warnings with your team, or explore Demo Mode first to see how the analysis works.
Start a free trial of CADY or contact the CADY team to see it on your own design.
Frequently Asked Questions
What are the most common mistakes in PCB schematics?
Common mistakes in PCB schematics include power pins connected to the wrong voltage rail, incorrect resistor or capacitor values on IC configuration pins, discrete parts chosen on DC ratings alone, mis-assigned digital interface pins, unintended net connections and poorly matched TVS diodes. Many can pass a basic ERC, so check each one against the component datasheet before layout.
Why doesn’t ERC catch power rail voltage mismatches?
A basic ERC usually does not catch power rail voltage mismatches because it checks whether pin electrical types may connect. Unless the tool has voltage-limit rules for the part, a 5V rail on a pin rated for 3.6V maximum looks like a valid power connection. Catching it requires comparing the rail voltage with the datasheet ratings.
How do you check a schematic against component datasheets?
To check a schematic against component datasheets, compare every supply pin with the recommended operating conditions, recalculate external component values with the datasheet equations, and confirm each interface pin’s function at both connected devices. Then check unused pins against the pin descriptions and compare protection parts with the interface’s voltage, capacitance and test requirements.
How do you choose a TVS diode for a USB interface?
To choose a TVS diode for a USB interface, select a reverse working voltage above the line voltage, compare clamping voltage at the relevant pulse current and waveform, check the ESD withstand rating, and keep capacitance low enough for the data rate. Then verify the assembled port, including connector and PCB loading, against the USB 2.0 high-speed requirements.
Can automated tools find schematic errors that ERC misses?
Automated tools can find many schematic errors that ERC misses when they have access to datasheet information. CADY, for example, reads component datasheets automatically from an uploaded netlist and BOM and applies more than 1,000 rules to flag issues such as voltage mapping and connection integrity errors. Engineers then review the flagged items and make the final design decisions.