Checks, previews and export

Run ERC and DRC, inspect previews and export the intended revision.

Linux AMD64, Linux ARM64, Windows x64 · Release 0.1.5

On this page

Choose the right check

Electrical Rules Check (ERC) inspects the schematic against configured electrical rules. Design Rules Check (DRC) checks the board against its configured design rules. Neither proves that the circuit will perform its intended function, tolerate a fault or be accepted by a manufacturer.

Before validation, resolve missing symbols and footprints, confirm the correct project and save the intended revision. In an Agent workflow, inspect the isolated candidate's results, not an older report from your trusted project.

Run and inspect ERC

Open the schematic editor and use Inspect → Electrical Rules Checker. Run the check and select a reported finding to locate its pins, symbols or nets. Read the specific explanation and decide whether the design or rule configuration needs correction.

Do not silence a warning just to obtain zero findings. Power flags, pin types and intentionally unconnected pins must match the circuit's actual intent. Record justified exclusions so another reviewer can understand them.

Run and inspect DRC

Open the board editor and use Inspect → Design Rules Checker. Check the configured clearances, net classes and board constraints, then run DRC. Inspect each reported issue in the board view.

A board generated from a different schematic revision may look plausible while being electrically inconsistent. Confirm schematic-to-board synchronization before trusting results. A clearance passing the configured rule does not establish that the rule meets your voltage, fabrication or regulatory requirements.

Read Agent validation evidence

Expand the relevant tool event or open Results in Changes. Verify the tool succeeded, the expected files were checked and the result belongs to the candidate you're reviewing. Distinguish:

  • Pass: the configured check ran successfully and met its recorded conditions.
  • Findings: the check ran and reported issues to review.
  • Failure or unavailable: the check did not establish a result, for example because a tool or library is missing.

A process exit status alone can be insufficient. Read the report and affected objects. If a preview is too large or cannot render, retain the error and inspect the native file; do not substitute an unrelated image.

Preview and export

Use the schematic, board and available 3D views to inspect the intended revision. Keep source revisions associated with exported SVG/PDF previews, BOMs, plots and drill files.

For board manufacturing output, use the board editor's File → Plot and drill-generation controls. Select the required layers, origin, units and output directory for your manufacturer. Review the resulting files independently before sending them anywhere. This guide does not supply universal manufacturing settings.

Expected outcome

You should have an identifiable source revision, the actual reports, explained findings and the previews or exports needed for review. If any are missing, keep the candidate isolated and repair the validation environment or narrow the claim. Continue with change review, not automatic approval.

Search documentation

Type to search the TraceForge guides.