Open PR #4 draft PR #5 draft feature request

standard-lane: structured fields for the limits fab checks compare (silk text, pad hole to hole, max drill, min board, recommended ring, heavy copper)

Colby Knox · 14d ago

From standard-lane, the thread that keeps adom/eda-bridge-standard and its shared checks engine (adom-eda-checks).

The engine's fab_check now takes its limits only from this page: one record from rules/records/<vendor>.json goes in as the input, and every finding names the record's source URL and read date. Nothing is hard-coded anymore. The Altium bridge used to carry its own copy of JLCPCB's numbers, read 2026-10-23.

The engine maps the record's fields and never parses notes. That leaves a few limits it can't check, because across the 56 records they exist only as prose:

Limit the check compares Where it is today Field I'd suggest
Minimum silkscreen text height notes, plus silkscreenPolicy on 2 records (JLCPCB 0.8 mm per the latest commit) silkTextHeight {mm}
Pad hole to pad hole the condition of holeToHole ("pad hole to pad hole is 0.45 mm") holeToHolePad {mm}, keeping holeToHole as via to via
Largest drill before routing drillRange on 2 records maxDrill {mm} on all
Minimum board size not recorded minBoardSize {xMm, yMm}
Recommended annular ring, not just the absolute minimum annularRing.note ("recommended 0.25 mm") annularRing.recommendedMm
Track and gap for heavier copper notes ("2 oz: 0.16/0.16 mm ...") one record per copper weight, or byCopperOz {"2": {minTraceWidthMm, minSpacingMm}}

Optional fields are fine. The engine reports a limit the record doesn't give as not checked, and never guesses one. If you'd rather keep these in notes, say so and I'll leave them out.

0 Replies

Josh Aberdeen mentioned this in pull request #3 · 9d ago
Josh Aberdeen mentioned this in pull request #4 · 9d ago
Josh Aberdeen mentioned this in pull request #5 · 9d ago
Josh Aberdeen mentioned this in pull request #6 · 9d ago

Log in to reply.