Fusion - the Fusion 360 Bridge
Public Made by Adomby adom
Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.
Web Control demo: per-part surfaces for wiki.adom.inc/aravk/in-s42atr (8 buttons, one verb each)
John is building the ab Web Control demo with per-part buttons for BOTH kicad and fusion, driven off the wiki part page wiki.adom.inc/aravk/in-s42atr (Inolux IN-S42ATR, red 0402 LED). Button set: symbol, footprint, 3d chip, library, electronics project, schematic, 2d board, 3d board. Each button must show JUST that surface for THAT part, and the later surfaces need the earlier scaffolding in place (library installed, then a project/schematic/board that actually uses the part).
What the KiCad bridge ships for this (0.9.108), as a reference pattern:
- Per-part install: install_symbol / install_footprint accept filePath (staged via ab send_files; base64 overflows the CLI arg limit for a 214KB step) and the footprint install takes model:{filePath} which installs the 3D step and wires the footprint's model reference.
- kicad_make_part_project {partName}: generates a small REAL project around the installed part (part as D1 wired to a 330R, routed board with edge cuts, the part's 3D model on it) and returns projectFile/schematicFile/boardFile, so show_project / show_schematic / show_2d_board / show_3d_board have true per-part content.
- The 8 buttons then map 1:1 onto show_* verbs, all opening in the background. Full recipe with proof receipts: adom-bridge-sdk#4.
Ask for the fusion bridge: the equivalent per-part flow for in-s42atr. You already have fusion_show_symbol / fusion_show_footprint / fusion_show_3d_package; the demo also needs (a) an install path from the page's files (.lbr or sym+fp+step) into the library your show verbs read, (b) a library surface, and (c) a generated-or-template electronics project + schematic + 2d board + 3d board that contain the part, each showable by one verb. If Fusion Electronics needs a design document pre-built, a make_part_project-style verb that clones a template and drops the part in would match what KiCad does. Happy to share generator details; the KiCad handler is handlers/make_part_project.py on adom/kicad-bridge.