Hi everyone,
Since I wanted to use some of Bambu Studio’s slicing features, I developed a compatibility package using vibe coding. This allows Bambu Studio to configure the U1 for slicing and enables direct printing over a local network.
I’m a programming beginner, so there may still be some bugs. Feel free to try it out, and I’d also welcome anyone to fork this project for further development.
I hope this project doesn’t die out before people get the integration they want into the Bambu Slicer. Unfortunately, I’m not a programmer and can’t contribute from that side.
Apparently only available for Windows.
…Indeed, I developed it on Windows.
Excellent compatibility pack, looking forward to updates and improvements from the experts.
Hi everyone,
The compatibility package has been updated with a bridge server that connects Bambu Studio to the printer. Feel free to try it out and report any bugs to me.
Thanks
Hi,
I’ve tried installing the package and Bambu Studio detects it just fine. I’m able to add the Snapmaker U1 without any issues.
However, when I start the Bridge Server, I get a Windows Script Host syntax error:
Error: 800A03EA
Has anyone else run into this problem or knows how to fix it?
Thanks
This is a BUG. Root cause: The expanded $nodePath contains parentheses, which VBScript does not recognize.
800A03EA is a VBScript syntax error, occurring in the start-hidden.vbs file.
The issue is in \[install.ps1:370\]
$vbsContent = @"
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run """$nodePath"" ""$bridgeDst\server.js""", 0, False
"@
PowerShell’s here-string expands the $nodePath and $bridgeDst variables. If the path contains parentheses (e.g., C:\Program Files (x86)\nodejs\node.exe), the expanded VBS content becomes:
WshShell.Run """C:\Program Files (x86)\nodejs\node.exe"" ""C:\Program Files\Bambu Studio\bridge\server.js""", 0, False
VBScript parses the parentheses in (x86) as function call syntax, causing the 800A03EA syntax error.
Root cause: The expanded $nodePath contains parentheses, which VBScript does not recognize.
Scope of impact:
C:\Program Files (x86)\nodejs\ (32-bit installation or certain NVM configurations)install.ps1 and reinstall.ps1 have the same issue (lines 370 and 404)Fix direction: In VBS, concatenate the path using a variable to avoid parentheses appearing directly in the Run parameter, for example:
Set WshShell = CreateObject("WScript.Shell")
Dim nodePath, scriptPath
nodePath = "C:\Program Files (x86)\nodejs\node.exe"
scriptPath = "C:\Program Files\Bambu Studio\bridge\server.js"
WshShell.Run """" & nodePath & """ """ & scriptPath & """", 0, False
Alternatively, use WshShell.Exec / cmd /c to start indirectly.
I’ve already tried to fix it. You can download the latest version from GitHub and run the reinstall command.
hi vitas i tried it and to this point i have this error.
and at the install.bat file it would come out with one data.
[1/10] Detecting BambuStudio...
Found: C:\Program Files\Bambu Studio
Reinstall Snapmaker U1 profiles + Bridge Server? (Y/N): y
[2/10] Stopping Bridge Server...
No Bridge process on port 13628 (OK)
[3/10] Removing old profiles...
Removed Snapmaker.json
Removed Snapmaker\ directory
No old profiles found (OK)
[4/10] Clearing BambuStudio system cache...
No system cache found (OK)
[4/10] Preserving user custom presets...
User presets directory found (preserved)
[5/10] Refreshing BambuStudio.conf cache...
[!] Failed to parse BambuStudio.conf, skipping (user data preserved)
[6/10] Patching user machine configs (print_host -> Bridge)...
No user machine configs needed patching (OK)
[7/10] Installing profiles...
Snapmaker.json
Snapmaker\ directory (103 files)
[8/10] Reinstalling Bridge Server (Node.js)...
Bridge files copied to C:\Program Files\Bambu Studio\bridge
Web UI files copied to C:\Program Files\Bambu Studio\bridge\web
Node.js found: C:\Program Files\nodejs\node.exe
Node.js version: v26.4.0
Installing npm dependencies...
C:\Program Files\nodejs\npm.ps1:3
Set-StrictMode -Version 'Latest'
^^^^^^^^
System.Management.Automation.RemoteException
SyntaxError: Unexpected string
at wrapSafe (node:internal/modules/cjs/loader:1876:18)
at Module._compile (node:internal/modules/cjs/loader:1918:20)
at Object..js (node:internal/modules/cjs/loader:2084:10)
at Module.load (node:internal/modules/cjs/loader:1666:32)
at Module._load (node:internal/modules/cjs/loader:1447:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:260:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47
System.Management.Automation.RemoteException
Node.js v26.4.0
npm dependencies installed
Created hidden launcher: C:\Users\ASPL\AppData\Roaming\BambuStudio-Bridge\start-hidden.vbs
Node.exe path in launcher: C:\Program Files\nodejs\node.exe
Updated startup shortcut
[9/10] Verifying...
Profile verification passed!
Bridge Server (Node.js): installed
[10/10] Starting Bridge Server...
Bridge Server starting...
Verifying Bridge is listening on port 13628...
[!] Bridge may not have started correctly.
Try running manually: node "C:\Program Files\Bambu Studio\bridge\server.js"
This was caused by the bridge not starting correctly.
The solution provided by AI was to downgrade Node.js.
Problem Analysis
Root Cause: Line 354 of install.ps1 calls npm incorrectly
Key code:
PowerShell
$npmCmd = (Get-Command npm -ErrorAction SilentlyContinue)
...
& $nodePath $npmCmd install --production
On Node.js v26.4.0, Get-Command npm resolved to npm.ps1 (a PowerShell script) instead of the traditional npm.cmd. As a result, the actual command executed became:
Plain Text
C:\Program Files\nodejs\node.exe "C:\Program Files\nodejs\npm.ps1" install --production
Node.js attempted to parse npm.ps1 as a JavaScript file, but the first line was PowerShell syntax: Set-StrictMode -Version 'Latest'. Naturally, this resulted in a SyntaxError: Unexpected string.
The npm dependencies were never successfully installed (the node_modules directory was empty). When Bridge started, it could not find dependencies like Express, and thus could not listen on the port.
Open PowerShell as an administrator and run:
PowerShell
cd "C:\Program Files\Bambu Studio\bridge"
npm.cmd install --production
Or use directly:
PowerShell
& "C:\Program Files\nodejs\npm.cmd" install --production
After installing the dependencies, Bridge will start normally.
Node.js v26 is an unconventional version released in October 2026, with changes to how npm is packaged. It is recommended to uninstall v26.4.0 and install Node.js v22 LTS:
install.batnpm.cmdCall the cmd version of npm directly in PowerShell:
PowerShell
npm.cmd install --production
Executing this after switching to the installation directory is more reliable than node npm.ps1.
One-sentence Root Cause: On v26, Get-Command npm returns npm.ps1, and the script uses node.exe to execute the .ps1 file. Node.js does not recognize PowerShell syntax and throws an error directly. Using npm.cmd (a batch wrapper) bypasses this issue.
There’s another bug within the system after it has successfully been updated that the orca and bambu could live view.
all the shortcut keys like move rotate cut all those are not able to work anymore.
Not sure. Are you talking about a Windows update?
It’s working fine for me right now.
Currently, this compatibility package automatically retrieves the device’s IP address via a script. Could you check if the retrieved IP differs from the actual device IP?
I’ll see if I can adjust how the IP is obtained.
In the meantime, you can try reinstalling to see if it picks up the wrong IP.
I think I can add an option to manually modify the device IP.
Under normal circumstances, the compatibility package should display the device IP and show that it is connected.
yes i just double checked from the router the ip was wrong but very weird thing is that i can view it being online and etc. but only uploading and print files cant work
basically what i was facing is that i can slice the file i can see the file converting the plate into U1 plate but i cant upload because the IP address was wrong by 1 number. it was suppose to send to 240 instead of 241. the weird thing is that the live view function works even though the ip was at the wrong address.
The slicing feature does not rely on the device being connected.
A proper device connection is only required when data transfer or device operations are involved.
Feel free to report any bugs to me.
how do i get the bug to be fixed or able to key the ip address manually? im stuck at this part right now
