Fusion - the Fusion 360 Bridge

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -13,11 +13,27 @@ chip-fetcher  ->  adom-symbol   -> .kicad_sym  ┐                   (3D STEP/glb provided)       ┘   (2D: symbol+package+connects)     (Content Manager) ``` -- **chip-fetcher** pulls a multi-CAD vendor bundle for an MPN (EAGLE, KiCad, Altium, ... AND a `3D/<MPN>.stp` STEP plus a `.glb`). Its library lives at `chip-fetcher/library/<MPN>/` (e.g. `nRF54L15.step`, `nRF54L15.glb`). chip-fetcher runs as a live app (the viewer is the `chip-fetcher` pup session); it is the content source.-- **adom-symbol** (`adom-symbol create` / `render-ds2sf`) makes the schematic **symbol** as a `.kicad_sym`. It is symbol-only: it does NOT touch STEP, 3D, or URNs.-- **adom-footprint** (`adom-footprint create` / `render-ds2sf`) makes the PCB **footprint** as a `.kicad_mod`. Footprint/2D-only, no 3D.-- **adom-lbr generate** `--sym NAME.kicad_sym --fp NAME.kicad_mod -o NAME.lbr` assembles the EAGLE `.lbr`: `<symbol>` + `<package>` (2D footprint) + `<deviceset>` with the connects. **It is 2D-only** (its `_fp_content`/3D path is unimplemented). The package it writes is a **placeholder** for 3D (see section 4). Validate with `adom-lbr validate NAME.lbr` -> "valid EAGLE .lbr with complete deviceset".-- **fusion_open_lbr** imports the `.lbr` into Fusion's Electronics **Library editor** (Content Manager). You then see the deviceset / symbol / package, and can place the part.+> ⛔ **USE THE CURATED `.fusion` VARIANT, NOT A RAW VENDOR DOWNLOAD.** chip-fetcher's library+> (`chip-fetcher/library/<MPN>/`) carries per-EDA variants. For Fusion, feed adom-lbr the+> **`<MPN>.fusion.kicad_sym` + `<MPN>.fusion.kicad_mod`** (Adom's `adom-sfconvert`-tuned files) and+> pair them with **`<MPN>-named.step`** (the curated 3D). Building from a raw `/tmp` vendor+> `EAGLE/*.lbr` or the thin `manufacturer.step` gives a footprint/3D mismatch AND the vendor `.lbr`+> fails `Create3DPackage`'s XML parser. (Convention confirmed in `chip-fetcher/src/thumbnails.rs`.)++- **chip-fetcher** pulls a multi-CAD vendor bundle for an MPN. Its curated library is at+  `chip-fetcher/library/<MPN>/` with variant files: `.fusion.*` (use these for Fusion), `.manufacturer.*`,+  `.altium.*`, `.ds2sf.*`, plus `<MPN>-named.step` (3D with the part number embossed) and render SVGs.+- **adom-symbol** / **adom-footprint** make the `.kicad_sym` / `.kicad_mod` (symbol / footprint, 2D only).+- **adom-lbr generate** `--sym <MPN>.fusion.kicad_sym --fp <MPN>.fusion.kicad_mod --name <MPN>` assembles+  the EAGLE `.lbr` (symbol + footprint + deviceset). **2D-only**, no 3D/URN; the 3D is attached in Fusion+  (sections 4-6). Validate with `adom-lbr validate`. **Inspect it visually**: `adom-lbr serve --port 8785+  --file <MPN>.lbr` run FROM the library dir (so it finds the render SVGs) gives a symbol | footprint | 3D+  + pin-map viewer - open it in pup to confirm the right footprint before touching Fusion.+- The **`-named.step` part-number emboss** is made by **`service-step2glb/api/occt/occt_name_on_chip.py`**+  (OpenCASCADE relief on the top face), driven by `chip-fetcher/scripts/occt-name-on-chip.py`.+- **fusion_open_lbr** imports the `.lbr` into Fusion's Electronics Library editor.++See **[FUSION_3D_FINDINGS.md](../../FUSION_3D_FINDINGS.md)** for the full live findings log.  ## 2. Opening a .lbr in Fusion (verified working)