app

adom-pin1-truth

Public Unreviewed

by Kyle Bergstedt

CLI shim over the pin-1 location dataset for KiCad standard footprints. One arg in (Library/Footprint), one JSON line out ({x_mm,y_mm,z_mm}). v0.2.0: fuzzy fallback strips _EP*x*mm and _ThermalVias su

Overview Files Skills Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity
Propose a change
Name Last commit message Last updated
adom-pin1-truth Migrate asset from Helium wiki 1mo ago
install.sh Add adompkg installer files 1mo ago
package.json Add adompkg installer files 1mo ago
page.json Remove internal identifiers from page.json 11d ago
README.md Initial commit: app/adom-pin1-truth 1mo ago
SKILL.md Add adompkg installer files 1mo ago
uninstall.sh Add adompkg installer files 1mo ago

adom-pin1-truth

CLI shim over the pin-1 location truth dataset for the KiCad standard footprint library.

Usage

adom-pin1-truth <Library>/<Footprint>

Single positional arg, same shape consumers already pass to step2glb from-library.

Output (stdout, single JSON line):

{"x_mm":-0.51,"y_mm":0.0,"z_mm":0.0}

Pin-1 location in the footprint's local frame (chip body at origin, +Z up). The consumer parents a sphere to the part mesh at these coords; rotation/mirroring happens for free.

Unknown footprint: exits non-zero with a one-line stderr message and no stdout. The consumer can fall back to its own pad-1 derivation.

Backed by

  • 14,884 KiCad-standard footprints parsed at build time from pin1-truth.json
  • Source: github.com/adom-inc/adom-pin1-truth

Exit codes

Code Meaning
0 Real answer printed to stdout
1 Footprint not in the dataset
2 Bad CLI input