Skip to main content
On this pageBefore you startFollow the stepsCheck your resultExample filesTroubleshooting

Validation

Run and triage DRC

Run the design rules check on the board, inspect each violation, fix it, and re-run.

What you will accomplish

A DRC result with no errors and only warnings you have reviewed.

Before you start

  • A saved PCB
  • Design rules set in Board Setup

Applies to: Resin web app

Follow the steps

  1. 1

    Run DRC

    In the PCB tab choose DRC in the toolbar and then Run DRC, or right-click the canvas and choose Run DRC. The panel shows Running design-rule checks... until it finishes.

    PCB > DRC > Run DRC

    Expected result

    The panel shows All checks passed or a list of violations.

  2. 2

    Open each violation

    Click a violation to select the objects involved on the canvas. Each row states the rule, the severity, and the location. Common findings: clearance between tracks or pads, track width below the net class minimum, unconnected items, and courtyard overlap.

    DRC panel

    Expected result

    You know which objects each violation refers to.

  3. 3

    Fix the geometry

    Move or reroute the tracks, vias, or footprints involved. If a violation comes from a rule that is stricter than your fabricator needs, change the rule in Board Setup > Design Rules rather than the geometry, and expect the panel to mark results as stale.

    PCB canvas

    Expected result

    Each edit corresponds to a violation you intend to clear.

  4. 4

    Re-run

    Press R or choose Run DRC again. Results are marked stale after any board or rule edit, so re-run before you trust the count. Use Export to save the report as TXT or HTML.

    DRC panel

    Expected result

    Errors are zero and the remaining warnings are ones you have reviewed.

Check your result

  • DRC run
  • Every violation opened
  • Fixes made
  • Re-run after the last edit
  • Zero errors

Example files

All 241 published findings

CSV / finding-level rows · Published evidence record

Finding-level export with run, severity, diagnostic code, rule category, message, and available project-object context.

Rows come from compact fixtures; no professional routed-board case is included.

Complete check reports

JSON / 6 runs · Published evidence record

Source-bound checker outputs behind the finding-level CSV and the run summary.

One reported condition may share a root cause with others; rule coverage is specific to these fixtures.

Troubleshooting

Find the symptom, apply the fix, and repeat the affected check.

Run DRC is disabled

No board is open, or the project is read-only for your account.

The panel says results are stale

The board or rules changed since the last run. Run DRC again.

A valid track is flagged

Check which net class the track belongs to and the rule the violation names. The rule may be stricter than intended.

Fixing one violation created another

Moving a track can push it into a neighbour. Undo and route with more room, or check the clearance rule.

DRC is clean but the fabricator rejects the board

DRC checks the rules you set. Compare them with the fabricator's published minimums in Board Setup.