A boardview for the wrong revision is more dangerous than no boardview at all, because it looks right. Most of the board matches, so you trust it — until you probe or desolder a part that, on your revision, sits a few millimetres away or does not exist. Matching the revision takes a few minutes and should become a habit.
Why revisions differ physically
Between revisions, ODMs move, add and remove parts far more often than they change the circuit. Typical layout changes include:
- capacitors added around a regulator to fix noise or ripple;
- a MOSFET or regulator replaced by a part with a different package;
- connectors shifted to fit a new chassis;
- components moved away from a hot spot or a screw boss;
- an entire area reworked for a new processor or memory type.
The schematic may change only slightly while the boardview changes in dozens of places. That is why revision matters even more for boardviews than for schematics — see Schematic Revisions: Why Rev 0.3 vs Rev 1.0 Matters for the schematic side.
Step 1: read your board's revision
Find the revision on the PCB, next to the board code:
| Board type | Where the revision is | Example |
|---|---|---|
| Compal / LCFC | After the code | LA-D312P REV 1.0, NM-A841 REV 1.0 |
| Dell (Compal) | Build stage next to the revision | REV 1.0 (A00) |
| Quanta | Letter inside the part number | DA0R63MB6F1 = revision F |
| Inventec | Suffix after the number | 6050A2412601-MB-A02 |
| Wistron | Digit after the project number | 16820-1, 13323-2 |
| Asus | After the model and "MB" | X540MB REV 2.0 |
| Gigabyte / desktop | Near the model name | GA-H61M-DS2 REV 1.1 |
Write the revision down together with the board code.
Step 2: read the boardview's revision
Check the archive and file names first — REV 1.0, R2.0, rA00, the Quanta letter. If the name does not say, the boardview itself sometimes contains a title, a revision field or a PCB part number in the board outline layer. When there is no revision information at all, you will rely on the physical comparison in Step 3.
Step 3: compare landmarks
With the boardview open and the board under good light, compare five or six features. Each takes seconds:
- Board outline — notches, cut-outs and the overall shape.
- Mounting holes — number and positions.
- Connectors — battery, display, keyboard, fan, daughterboards, ports.
- Big chips — CPU, GPU, PCH, EC, and their orientation.
- Power section — positions of the large inductors and MOSFETs around the CPU.
- A few readable designators — find two or three silkscreen labels on the board and check they sit at the same places in the boardview.
If all of them match, you can trust the file for positions. If the outline and connectors match but the power section differs, you have a close revision: fine for orientation, not for locating individual power parts.
Step 4: check the part you are about to touch
Before you probe a fine-pitch pin, lift an inductor or heat a capacitor, confirm that specific part:
- its outline and size on the board match the boardview;
- its neighbours are the same parts the boardview shows;
- if it has a silkscreen label, it matches the designator.
This one check prevents most revision-related mistakes, even when the rest of the board has not been compared.
Working with a close revision
Often the exact revision is not available. A close revision is still very useful if you treat it carefully:
- Use it for nets and orientation. Net names and which parts are on a rail rarely change.
- Verify positions before acting. Confirm each part you work on, as in Step 4.
- Expect extra or missing parts. A capacitor on your board that is not in the file is probably an addition in your revision.
- Prefer the newer of two close revisions when you have a choice; production boards are more often later revisions.
When two files for the same board disagree
Sometimes the catalog lists two boardviews for the same board code, and they differ. Usually one is a different revision, or one is a variant for a different configuration (with or without a discrete GPU). Compare both with your board using Step 3 and keep the one that matches better. Board pages list the revision of each file when the file name includes it.
Asus: model, MB revision and configuration
Asus boards add a twist: the part number 60NB0IQ0-MB1100 includes a configuration code after MB, and the file name often includes RAM and CPU details. Boards with the same first part (60NB0IQ0) share a layout; the configuration tail and the main board revision decide what is fitted. Asus boardviews are usually .FZ files, and the FZ guide covers matching them.
Example: a Quanta board with two revisions
The board on the bench reads DA0X81MB6E0 — revision E. The catalog has a boardview for revision D and another for revision F, but none for E.
- Outline and holes. Both files match the board outline and mounting holes. No help choosing yet.
- Connectors. Both match. The display and keyboard connectors sit in the same places.
- Power section. The D file shows two inductors next to the CPU where the board has three; the F file shows three. The F file is closer.
- Designators. Two silkscreen labels near the charger match the F file exactly and are rotated differently in the D file.
The technician uses the F file, notes "boardview rev F vs board rev E" on the job sheet, and confirms each part before touching it. When the fault turns out to be in the charger area — the part of the board that matched F exactly — the file proves completely reliable there.
The lesson: there is rarely a perfect file, but there is usually a best one, and a methodical comparison finds it in minutes.
A quick habit that prevents mistakes
Every time you open a boardview for a job, spend one minute on the outline, the connectors and one designator before you start. Note in your job sheet: "Boardview rev 1.0 vs board rev 2.0 — power section differs near PU12". The next technician (or you, next week) will thank you.
If you are new to boardviews in general, start with What Is a Boardview File and Why You Need One.
FAQ
My boardview matches the outline but not the parts. What now?
The board design is the same family but a different revision or variant. Use it for nets and orientation only, and confirm every part on the board before touching it.
Can I trust net names from a different revision?
Mostly. Net names are taken from the schematic and change far less often than positions. Still confirm critical nets by clicking a pad you can see on the board.
Why does my boardview show parts that are not on my board?
Either they are optional parts not fitted on your variant, or the file is for a revision that added them. The schematic's option markings tell you which.
Is a boardview from a sister model useful?
Only if the board code is the same. Two models with different board codes are different designs, even if they look alike.
Bottom line
Read the revision on the PCB, read it in the file name, then compare outline, connectors, big chips and a few designators. Trust a close revision for nets and orientation, and confirm each part on the board before you probe or heat it.