Open bug report

create emits resistor silkscreen through pads without collision hints

John Lauer · 1mo ago

adom-footprint 1.0.20; Linux/WSL2 kernel 6.18.33.2-microsoft-standard-WSL2; adom/codex context 0.1.22. No desktop Bridge is involved in this CLI reproduction. Observed 9 September 2026.

adom-footprint create --file TNPW0603100KBEEA-footprint-input.json --out generated exits successfully but emits a full F.SilkS rectangle through both resistor lands. The attached input follows Vishay document 28950: two rectangular 0.90 x 1.00 mm pads at X +/-0.80 mm, Y=0; body 1.55 x 0.85 mm.

The generated silk rectangle has X +/-0.895 and Y +/-0.545 mm, stroke 0.12 mm. Its vertical segments lie inside the pad copper spans X 0.35..1.25 / -1.25..-0.35, Y -0.50..0.50. The top/bottom strokes also reach within 0.485 mm of center, intersecting the pad edge. No warning or error is returned.

Expected: clip or move silk around expanded copper/mask clearance, or return explicit collision diagnostics and an actionable AI hint naming the pad, silk item and clearance. Please keep F.Fab at the true body size and distinguish generation success from fabrication validation.

The project derivative uses external top/bottom silk lines at Y +/-0.75 mm; it is attached for comparison. The original generated file and exact input are attached, so this can be reproduced without a screenshot or desktop application. The rendered component can be inspected at https://wiki.adom.inc/adom/tnpw0603100kbeea . Native library parity and factory validation remain separate.

This concerns generated geometry, separate from existing issue #2 about dropping layer graphics in render/embed. Also, create --help lists --out without saying it is an output directory; a .kicad_mod-looking argument creates a directory of that name. Please clarify the hint/help.

TNPW0603100KBEEA-footprint-input.json

TNPW0603100KBEEA.kicad_mod

TNPW0603100KBEEA.kicad_mod

0 Replies

Log in to reply.