app
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.
← Commit history
Update 8 file(s)
8 files changed
+45−16
BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.93+1.9.94
adom-bridge-fusion-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "fusion360",- "version": "1.9.93",- "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.108/adom-bridge-fusion-v1.9.93.zip",- "sha256": "3d4cd2db076ef77e765f7b741980b27b64131ae07a918657d9083aefc1ffe158",- "size": 429364,+ "version": "1.9.94",+ "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.109/adom-bridge-fusion-v1.9.94.zip",+ "sha256": "741ce3bbd66767101138b5a0f02cecdb0dedaabb72a08788f2c2f79ac5048587",+ "size": 429895, "verbPrefixes": [ "fusion_" ],
bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "fusion360", "displayName": "Autodesk Fusion 360",- "version": "1.9.93",+ "version": "1.9.94", "description": "Drive Autodesk Fusion 360 from the cloud: launch Fusion, electronics board layout, design rules, exports (STEP/IGES/STL/3MF/USDZ/OBJ/DXF/DWG/Gerbers/BOM/CPL), fast APS server-indexed cloud search plus browse/recent/file-info/versions, cloud file download/upload and folder creation, and in-app parametric modeling (fusion_run_modeling_script). Never-charge: APS calls are capped to the free tier.", "homepage": "https://wiki.adom.inc/adom/fusion-bridge", "author": "Adom Inc.",
dashboard/Cargo.toml+1−1@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.9.108"+version = "1.9.109" edition = "2021" [dependencies]
install.sh+1−1@@ -21,7 +21,7 @@ echo "Installed fusion-bridge skills: $(ls "$PKG_DIR/skills" 2>/dev/null | tr '\ # binary (the three-artifact pattern: bridge zip -> ab, THIS pkg -> container skills + # this download, page media -> wiki). Per the wiki's PKG_VS_RELEASE policy, binaries are # platform-tagged RELEASE assets, never tarball content - the installer fetches them.-DASH_VERSION="1.9.108"+DASH_VERSION="1.9.109" DASH_URL="https://wiki.adom.inc/download/adom/fusion-bridge/${DASH_VERSION}/fusion-dashboard" DEST="" if [ -w /usr/local/bin ]; then DEST=/usr/local/bin
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "fusion-bridge",- "version": "1.9.108",+ "version": "1.9.109", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {
page.json+10−7@@ -1,6 +1,6 @@ { "slug": "fusion-bridge",- "version": "1.9.108",+ "version": "1.9.109", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {@@ -11,6 +11,10 @@ "uninstall": "./uninstall.sh" }, "tags": [+ "ab",+ "bridge",+ "fusion",+ "desktop-app", "fusion360", "autodesk", "cad",@@ -70,7 +74,10 @@ "build a basic parts library", "add a 3d model to a component", "make a fusion 360 library with 3d",- "set up the fusion bridge"+ "set up the fusion bridge",+ "fusion dashboard",+ "fusion status page",+ "open the fusion launch page" ], "discovery_pitch": "Use the Adom Bridge Fusion 360 bridge when the user wants to DRIVE Autodesk Fusion 360 from the cloud: open/search their team's Fusion cloud designs, lay out a PCB or do electronics, export STEP/IGES/STL/Gerbers/BOM, or build a component library with real rendering 3D. It runs Fusion on the user's own machine via Adom Bridge. NOT for web/browser/login/form-filling (that's the native-browser extension) and NOT for KiCad (that's the kicad bridge).", "brief": "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.",@@ -99,9 +106,5 @@ "label": "Part volume", "prompt": "How much material does each printed part in this assembly use?" }- ],- "author": {- "name": "John Lauer",- "email": "[email protected]"- }+ ] }
server.py+26@@ -2756,6 +2756,32 @@ def _diagnose_addin_timeout(command: str, original_result: dict) -> dict: }, } + # THREE faults live here now, not two, and BUSY is the one that looks most like death+ # (page issue #40). /status answers without taking the main-thread lock, so it can tell+ # us a long command is still running - while the command a caller just sent is queued+ # behind it and times out. Reporting that as "add-in not responding" is what made a+ # 5s-spaced test matrix conclude the add-in dies after one command: a single surface+ # measured 546s here, so nine minutes of perfectly healthy WORK reads as death.+ try:+ _st_busy = _check_addin_status(timeout=3.0)+ except Exception:+ _st_busy = None+ if _st_busy and _st_busy.get("busy"):+ return {+ "success": False,+ "error": "The add-in is BUSY running a long command, not dead - your command is "+ "queued behind it.",+ "errorCode": "fusion_addin_busy",+ "busyCommand": _st_busy.get("busyCommand"),+ "elapsedSeconds": _st_busy.get("elapsedSeconds"),+ "hostResponding": True,+ "_hint": ("Do NOT restart Fusion and do not treat this as a crash. Fusion runs one "+ "command at a time on its main thread, and some surfaces genuinely take "+ "minutes (a staged first-open has measured 546s here). WAIT and re-poll - "+ "fusion_state answers while the add-in is busy and reports mainThreadBusy "+ "with the running command. Only treat it as broken if elapsedSeconds keeps "+ "climbing past what fusion_state.timings says this machine has ever taken."),+ } # Health probe failed. TWO DIFFERENT FAULTS LIVE HERE and they need opposite # responses (page issue #38): the add-in being down is recoverable over IPC, a HUNG # HOST PROCESS is not. Reporting the second as the first sent a reader hunting a