PCB Net Tracing Explained

Introduction: What is Net Tracing?

Net tracing is the art of following electrical connections through a PCB to understand signal flow and identify faults. It's one of the most powerful diagnostic techniques in board-level repair.

When you trace a net, you're answering a simple question: "Where does this electrical signal go, and what does it connect to?"

In this guide, you'll learn:

• What nets are and why they matter
• How to trace power rails systematically
• How to follow signal paths from input to output
• How to identify shorts, opens, and faults using net tracing
• Real-world repair scenarios solved with net tracing
• Advanced techniques: constellation view, multi-board comparison

Understanding Nets: The Foundation

A net is an electrical connection. It might include:

• A pin on a microchip
• A copper trace on the PCB
• A via (connection between board layers)
• Pins on multiple other components
• A solder pad on a connector

In boardview, nets are usually shown as:

• Colored lines connecting components
• Highlighted paths when you click or search
• Named connections (like GND, 3.3V, DATA_IN)

Types of Nets You'll Encounter

Power nets: Carry voltage to components

• Examples: 3.3V, 1.8V, 5V, GND (ground)
• Usually thicker traces, more critical
• Failures here cause widespread system problems

Signal nets: Carry information between components

• Examples: CLK (clock), DATA, INT (interrupt), CS (chip select)
• Thinner traces, more numerous
• Failures here cause specific feature loss

Ground nets: Return path for electricity

• Often multiple groundplanes for stability
• If ground is broken, nothing works
• Ground shorts are catastrophic

Step 1: Starting Your Trace — Choose Your Net

Where to Start?

Choose a net based on your diagnosis:

• Device won't power on: Start with main power net (VBATT → 3.3V rail)
• No display: Trace display power (usually 5V or 3.3V for backlight)
• No audio: Trace audio power and codec signals
• USB not detected: Trace USB power and signal lines
• Intermittent behavior: Trace power supply to the failing component

Using Boardview to Search Nets

In boardview software like BoardScope:

1. Right-click on any component pin
2. Select "Highlight Net" or "Search"
3. The entire net lights up in a color
4. You can now see every component connected to this signal

Pro tip: Some software shows "constellation view" — all connected components arranged as a diagram, making relationships clear.

Step 2: Tracing Power Paths

The Power Supply Chain

On modern devices, power follows a strict hierarchy:

1. Battery/USB: Primary power source (VBATT)
2. Protection: Diodes, fuses protect against reverse polarity
3. Power Management IC (PMIC): Converts battery voltage to required rails
4. Regulators: Individual regulators for each voltage rail
5. Capacitor banks: Filter and stabilize voltage
6. Components: Processors, memory, RF chips receive regulated power

Tracing Example: MacBook Power

Scenario: MacBook won't charge

1. Start at battery connector (power source)
2. Trace VBATT net through protection diode
3. Follow to Power Management IC (usually labeled PMIC or SMC)
4. Check for voltage at PMIC input (should be 11-13V)
5. If voltage present at input but missing at output, PMIC is damaged
6. If voltage missing at input, check protection diode (might be shorted)
7. Replace faulty component, retest

Step 3: Tracing Signal Paths

Clock Signals

Clock signals are critical. They synchronize all digital operations.

• Usually named CLK, XCLK, or with frequency (32MHz, 50MHz)
• If clock fails, the processor can't execute instructions
• Device appears completely dead

Trace clock from oscillator → processor. If missing, the oscillator crystal or its supporting components are likely damaged.

Data Lines

Data lines carry actual information (memory reads/writes, display data, USB packets).

Example: NAND memory data lines

• Name: DATA0, DATA1... DATA7 (usually 8 lines for parallel connections)
• Route: Processor → NAND memory chip
• If broken: Device boots but can't read storage

Trace from processor through protective components (resistors, diodes) to the memory chip. A short here would prevent data communication.

Interrupt & Control Lines

These signal events that need attention:

• INT (interrupt) — Tells processor something happened
• CS (chip select) — Enables one component to communicate
• WR (write), RD (read) — Control data direction

Trace these from source to destination. A broken control line means the component can't be addressed.

Step 4: Identifying Common Faults Using Net Traces

Open Circuit (Broken Connection)

Symptom: Component receives power but no signal

How to detect via net tracing:

• Trace the signal net
• Measure voltage at each component pin along the path
• Find where voltage disappears
• That's where the trace is broken (burnt trace, disconnected pad, broken via)

Short Circuit (Unintended Connection)

Symptom: Device draws excessive current, components get hot, system resets randomly

How to detect via net tracing:

• Trace the power rail
• A short means power (3.3V) is connected to ground
• The voltage collapses from 3.3V to near 0V
• Measure along the trace — find where voltage drops
• That location has the short (damaged capacitor, burnt resistor, bridged solder)

Weak Connection (High Resistance)

Symptom: Intermittent failures, performance slowdown, occasional crashes

How to detect via net tracing:

• Trace the signal net
• Measure voltage along the path under load
• High-resistance connections show voltage sags (droop)
• The component with the worst droop is the culprit (oxidized pad, fractured trace, bad via)

Step 5: Advanced Net Tracing Techniques

Constellation View

Some boardview software shows a "constellation" of all components on a net, arranged in a circle or diagram. This shows relationships at a glance:

• All components on a net are grouped
• You can see which components share signals
• Makes multi-pin connections visible

Multi-Board Comparison

If you have a working board and a broken board:

1. Open both in boardview
2. Trace the same net on both boards
3. Compare the paths
4. Are there different components? Missing capacitors? Bridges?
5. The difference is often the fault

Measuring Under Load

Static measurement (board powered, nothing running): Gives baseline voltage

Dynamic measurement (board booting, running, processing): Shows real-world behavior

A voltage that looks good at rest might droop dangerously under load. Always measure during operation.

Real-World Repair Scenarios

Scenario 1: iPhone Won't Turn On

Customer complaint: Connected to charger, no response

Diagnosis approach:

1. Load iPhone schematic and boardview
2. Trace VBATT (battery voltage) from connector
3. Measure at each step: charger input, charging IC output, main power rail
4. Find the voltage drop — that's the faulty stage
5. If voltage present at charger IC input but missing at output, IC is bad
6. If voltage present at main power rail but device doesn't boot, check processor power sequence (multiple rails must come up in correct order)

Common root causes found via net tracing:

• Burnt charging diode (battery can't supply power)
• Shorted power capacitor (main rail collapses)
• Broken power IC (voltage not distributed)

Scenario 2: MacBook Kernel Panic During Boot

Customer complaint: Random crashes, sometimes boots, sometimes doesn't

Diagnosis approach:

1. Trace 3.3V rail (processor supply)
2. Measure voltage stability during boot
3. Look for droop or oscillation
4. Droop suggests weak power delivery — bad capacitor or connector
5. Oscillation suggests noise — bad filter or ground connection
6. Compare to working board if available

Common root causes:

• Swollen capacitor (increased ESR, poor filtering)
• Oxidized power connector (contact resistance varies with temperature)
• Fractured trace under processor (intermittent connection)

Scenario 3: USB Not Detected

Customer complaint: Device charges but computer doesn't recognize it

Diagnosis approach:

1. Trace USB power (usually 5V) — measure at USB connector
2. If power present, continue to USB controller IC
3. Trace USB data lines (D+ and D-)
4. These should go from connector through protection diodes to USB IC
5. Measure data line voltages (should oscillate during communication, DC at rest)
6. If data lines stuck high or low, communication circuit is damaged

Common root causes:

• Burnt USB protection diode (shorts data line to ground)
• Damaged USB IC or crystal
• Broken data trace from connector to IC

Tools That Make Net Tracing Easier

Boardview Software

Must-have features:

• Net highlighting (visual path display)
• Search functionality (find nets by name)
• Cross-reference with schematic
• Measurement logging (record voltages directly in the tool)
• Multi-layer support (trace through board layers)

BoardScope includes all of these and adds AI-powered fault suggestions.

USB Multimeter

Measure voltages while boardview shows the path. Log results directly in boardview for documentation.

Thermal Imaging

Hot spots often indicate shorts or high resistance. Correlate thermal image with net traces to pinpoint faults.

Logic Analyzer (Advanced)

Capture signal behavior on data and clock lines. Understand timing issues, verify communication.

Common Mistakes to Avoid

Mistake 1: Tracing visually without measuring — A net might look connected but have high resistance. Always measure.

Mistake 2: Ignoring ground connections — Ground is as important as power. Trace ground paths too.

Mistake 3: Static-only testing — Measure voltages while the device is working (booting, running apps).

Mistake 4: Not consulting the schematic — Boardview shows connections; schematic explains WHY. Use both.

Mistake 5: Assuming the first fault is the only fault — Water damage often causes multiple shorts. Keep tracing.

Practice Exercises

Master net tracing by practicing on real boards:

1. Download 3 different board files (iPhone, MacBook, game console)
2. Search for "GND" — see how ground connects everything
3. Search for "3.3V" — trace the main processor power
4. Search for "CLK" — understand clock distribution
5. On a broken board, trace power from battery → processor, measuring at each stage
6. Compare traces on working vs broken board for the same device

Summary

• Nets are electrical connections in PCBs
• Net tracing follows signal paths to diagnose faults
• Power net tracing finds supply problems
• Signal net tracing finds communication failures
• Always measure voltages as you trace
• Boardview software makes tracing visual and fast
• Combine with schematic for complete understanding
• Practice on multiple board types to build intuition

Net tracing is a skill that improves with practice. After 10-15 boards, you'll be spotting faults in minutes.