Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

How DRC works

What the design rule check (DRC) checks, the four harness states, and how results show on the canvas and in Board Review

Goal

Understand what Protoboard's design rule check (DRC) looks at, what each result means and where you see it.

When DRC runs

DRC runs continuously. Every change to a part, harness or allocation updates the results within a moment. There's no button to press, and the same board always gives the same result.

What DRC checks

For each harness:

  1. Is there an interface link? A harness with no interface pair is not configured.

  2. Are the two interfaces compatible? Protocol type, roles, domain, electrical ranges (for example voltage ranges that don't overlap) and physical connector, when the part definitions specify them.

  3. Is every required function wired? Each function the interface requires needs a function link on the harness.

  4. Does every function have a resource? Each required function needs a pin or port allocated on its part.

  5. Is each interface within capacity? A part can't carry more instances of an interface than its resources can back.

Optional functions don't need to be wired. With fan-out, every instance on the fanned side needs its own wiring and pins.

The four states

State
Colour
Meaning
Board Review lane

Configured

Green

All required functions are linked and allocated

(no issue)

Partially configured

Yellow

The interface link exists, but wiring or pins are missing, or an interface is over capacity

PARTIAL

Not configured

Grey

No interface link yet

BLOCKED

Incompatible

Red

The interfaces can't connect, or the parts share no compatible pair

BLOCKED

A one-sided link, where only one side has an interface because the other part isn't modelled yet, shows as partially configured. That's acceptable while you design; model the other side to reach Configured.

Over-capacity interfaces are also reported as blocking part issues.

In high contrast mode each state also gets its own line pattern, so state never depends on colour alone. The HARNESS LEGEND at the right of the canvas explains each state and its fix.

Where you see results

  • On the canvas: each harness is coloured by its state.

  • In Board Review: open Board Review in the left rail. Issues are listed under // DRC Issues, grouped as BLOCKED and PARTIAL, each with its reasons and a target icon that shows it on the canvas. See Board Review and review comments.

  • For agents: ProtoBot and MCP agents run the same check with run_drc.

The shield icon in the left activity bar is selected and the Board Review panel opens, listing one DRC issue under BLOCKED. On the canvas, the harness between a resistor and an LED is labeled INCOMPATIBLE.
Board Review with one blocked DRC issue.

Reading the reasons

Each issue lists why the harness isn't configured, for example:

  • No interface link

  • No compatible interface pairs found

  • Protocol type mismatch: i2c vs spi

  • Voltage ranges don't overlap: 4.5-5.5V vs 1.8-3.6V

  • Side A function 'i2c_sda' not yet assigned to a resource (0/1)

Some reasons confirm what does match (for example Matching domain: electrical); they're context, not problems. For fixes, see Fixing DRC failures. The full list is in DRC rules and severity.

What DRC doesn't check

DRC works from the part definitions on your board. It doesn't simulate circuits, check timing or bus loading, or catch a wrong value in a part definition. Check critical numbers against the datasheet, and report a problem if a library part is wrong.

Common failures

Every harness is grey

Drawing a harness doesn't choose what it carries. Select each harness and pick an Interface pair.

The issue doesn't clear after I fix it

Check that you're editing (the status pill says Editing) and that the change saved. If the reason mentions a function, look for a second instance or the other side of the harness.

Last updated