How to Use a Schematic and a Boardview Together

A schematic tells you how a board is supposed to work; a boardview tells you where everything is. Each one alone leaves you guessing. Used together, they let you go from "this rail is missing" to the exact pad you need to probe in under a minute — which is why most board-level technicians keep both open on two screens all day.

What each document gives you

The boardview's strongest feature is net highlighting: click any pin and every other pad on the same net lights up, on both sides of the board. That one function replaces a lot of page-flipping in the schematic. If you are new to boardviews, start with What Is a Boardview File and Why You Need One.

Set up your workspace

1. Use matching revisions. Open the schematic and boardview for the same board code and revision. Positions change between revisions; logic changes less.
2. Use two screens or a split screen. One for the PDF, one for the viewer. Flipping windows on a single small screen breaks concentration.
3. Flip the boardview to match the board. Most viewers can mirror the view so the bottom side looks the way it does when you turn the board over. Get this right before you start; it prevents most "the part is not where the boardview says" moments.
4. Keep a notes file. Write down net names and designators as you go. You will refer back to them when you measure.

Viewer installation and the basic controls are covered in OpenBoardView: Installation and First Steps.

Workflow 1: from the schematic to the board

Use this when you know what to measure but not where.

1. In the schematic, find the rail or signal you want — for example the output of the always-on regulator, or its enable pin.
2. Note the designator of a part on that net that is easy to probe: a capacitor, an inductor or a test point.
3. Search that designator in the boardview. The viewer centres on the part and highlights it.
4. Click the pad to confirm the net name matches the schematic.
5. Find the same spot on the real board using nearby large parts as landmarks, and measure.

Choose probe points sensibly: the larger capacitors on a rail are easier and safer to probe than the pins of a fine-pitch IC.

Workflow 2: from the board back to the schematic

Use this when the board tells you something first — a burnt part, a hot spot under the thermal camera, corrosion after a spill.

1. Find the part in the boardview by its location and read its designator.
2. Click its pins and note the net names.
3. Search the designator or the net names in the schematic to see what the part does.
4. Decide whether it is a cause (a shorted capacitor on a rail) or a symptom (a regulator that overheated because something downstream is shorted).

This workflow is how most liquid damage repairs start: you see corrosion, identify the nets it touches and check whether any of them are critical rails or signals.

Workflow 3: tracing a short

A short to ground on a rail is one of the most common faults. The schematic tells you which rail; the boardview tells you everything on it.

1. Measure the rail in resistance or diode mode against ground and confirm it is low.
2. In the boardview, highlight that net. Every capacitor, IC pin and connector pin on the rail lights up, often dozens of parts.
3. Use the schematic to divide the rail into sections. Inductors, ferrite beads, zero-ohm resistors and power jumpers split it into branches.
4. Isolate branches by lifting a jumper or inductor and measuring each side.
5. When you have narrowed it to one branch, use voltage injection, a thermal camera or freeze spray to find the warm part. See How to Find a Short Circuit on a Laptop Motherboard.

Without the boardview you would hunt for each capacitor on the rail page by page; with it you see the whole rail at once.

Workflow 4: following a missing signal

When an enable or power-good signal is missing, the schematic shows where it comes from and the boardview shows where to measure along the way.

1. In the schematic, follow the signal from the destination pin back to its source: through series resistors, level shifters or inverters.
2. List every part on that path and the net name on each side.
3. In the boardview, find the pull-up resistor or series resistor on each segment. Resistor pads are easy, safe probe points.
4. Measure each segment. The point where the signal disappears is the area to inspect.

Tips that save time

• Pin 1 matters. Boardviews mark pin 1 of each IC. Use it to orient yourself before probing chip pins.
• Designators usually match. The schematic and the boardview are exported from the same design, so PC113 is PC113 in both. When they do not match, you probably have different revisions.
• Net names can differ slightly. Some boardview formats shorten or modify names. Search for part of the name if the full one fails.
• Look at both sides. Many rails have parts on the bottom of the board, often directly under the chip they feed.
• Use diode readings if the file has them. Some boardviews include reference diode-mode values for each net. They are a helpful comparison, as explained in Using Diode Mode Values from Boardview Files.

When you only have one of the two

With only a schematic, you can still diagnose, but finding parts takes longer: use the board's silkscreen, landmarks such as connectors, and the fact that support parts sit close to the chip they serve. With only a boardview, net names tell you a lot — enable and power-good nets are often obvious from their names — but you lose component values and the reasoning behind each circuit. Search for both on the board page in the boardview section; files are often posted separately.

FAQ

Do I need a paid viewer to use schematics and boardviews together?

No. A PDF reader and OpenBoardView cover most boards. Paid viewers add more formats and features, but the workflow is the same.

The part is not where the boardview says. What is wrong?

Usually the boardview is for another revision, or the view is not mirrored for the bottom side. Check the board code and revision first, then the view orientation.

Can the boardview replace the schematic?

For finding parts and following nets, often yes. For understanding why a rail is missing — which enable controls it, what the expected voltage is — you need the schematic.

Which should I open first?

The schematic, to decide what to measure. Then the boardview, to find where. Going the other way works when the board shows you something first, such as a burnt part.

Bottom line

Let the schematic decide what to measure and the boardview decide where. Keep both on screen, match their revisions, mirror the view to match the board, and use net highlighting to see whole rails and signals at a glance. That combination is the core skill of board-level repair.