chore: upgrade StudioBridge v2.1.1 -> v2.1.2, add A1 fix guide and JAR auto-download
This commit is contained in:
ske087
@@ -16,6 +16,30 @@ set "ROOTDIR=%~dp0"
|
||||
REM Set the path to the portable-dist folder
|
||||
set "PORTABLE=%ROOTDIR%portable-dist"
|
||||
|
||||
REM ---------------------------------------------------------------------------
|
||||
REM JAR auto-download (StudioBridge 2.1.2)
|
||||
REM ---------------------------------------------------------------------------
|
||||
set "JAR_FILE=%PORTABLE%\StudioBridge-2.1.2.jar"
|
||||
set "JAR_URL=https://github.com/Rdiger-36/StudioBridge/releases/download/v.2.1.2/StudioBridge-2.1.2.jar"
|
||||
|
||||
if not exist "%JAR_FILE%" (
|
||||
echo [JAR] StudioBridge-2.1.2.jar not found.
|
||||
echo [JAR] Downloading StudioBridge 2.1.2...
|
||||
echo.
|
||||
powershell -NoProfile -Command "Invoke-WebRequest -Uri '%JAR_URL%' -OutFile '%JAR_FILE%'" 2>nul
|
||||
if not exist "%JAR_FILE%" (
|
||||
echo ERROR: JAR download failed. Please check your internet connection.
|
||||
echo You can also manually download StudioBridge-2.1.2.jar from:
|
||||
echo https://github.com/Rdiger-36/StudioBridge/releases/tag/v.2.1.2
|
||||
echo and place it in: %PORTABLE%
|
||||
pause
|
||||
exit /b 1
|
||||
)
|
||||
echo [JAR] StudioBridge 2.1.2 downloaded successfully.
|
||||
echo.
|
||||
)
|
||||
REM ---------------------------------------------------------------------------
|
||||
|
||||
REM ---------------------------------------------------------------------------
|
||||
REM JRE auto-download (Temurin 21 LTS for Windows x64)
|
||||
REM ---------------------------------------------------------------------------
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# StudioBridge
|
||||
|
||||
> **This portable distribution bundles StudioBridge v2.1.1** — the latest release from [Rdiger-36/StudioBridge](https://github.com/Rdiger-36/StudioBridge).
|
||||
> **This portable distribution bundles StudioBridge v2.1.2** — the latest release from [Rdiger-36/StudioBridge](https://github.com/Rdiger-36/StudioBridge).
|
||||
|
||||
With StudioBridge it is possible to make Bambu Lab 3D Printers visible in Bambu Studio or Orca Slicer, that cannot be automatically added by them.
|
||||
It is also possible to connect printers from other subnets or from accessible external networks (e.g. via VPN) or in your normal home network.
|
||||
@@ -23,11 +23,12 @@ Successfully tested on:
|
||||
- Linux Ubuntu 25.10 ARM and x86
|
||||
- MacOS Intel and M-Series
|
||||
|
||||
# Supported Printers (v2.1.1)
|
||||
# Supported Printers (v2.1.2)
|
||||
| Display Name | Model Code |
|
||||
|---|---|
|
||||
| A1 | N2S |
|
||||
| A1 Mini | N1 |
|
||||
| A2L | N9 |
|
||||
| P1P | C11 |
|
||||
| P1S | C12 |
|
||||
| P2S | N7 |
|
||||
@@ -89,8 +90,8 @@ StudioBridge.jar is built in Java, so a Java Runtime Environment (JRE) is requir
|
||||
2. Verify with `java -version`.
|
||||
|
||||
**Running the GUI:**
|
||||
1. Download `StudioBridge-2.1.1.jar` from the [GitHub releases page](https://github.com/Rdiger-36/StudioBridge/releases/tag/v.2.1.1).
|
||||
2. Double-click the `.jar` to launch, or run: `java -jar StudioBridge-2.1.1.jar`
|
||||
2. Download `StudioBridge-2.1.2.jar` from the [GitHub releases page](https://github.com/Rdiger-36/StudioBridge/releases/tag/v.2.1.2).
|
||||
2. Double-click the `.jar` to launch, or run: `java -jar StudioBridge-2.1.2.jar`
|
||||
|
||||
# FAQ
|
||||
|
||||
@@ -103,6 +104,17 @@ xattr -dr com.apple.quarantine /Applications/StudioBridge.app
|
||||
**Q: My Printer does not connect to Bambu Studio (Error Code -1)**
|
||||
A: Check that all printer information (IP, serial number, model) is correct. Try disabling/enabling Only-LAN-Mode. You can also try disconnecting the printer from the cloud and reconnecting it ([Issue #12](https://github.com/Rdiger-36/StudioBridge/issues/12)).
|
||||
|
||||
**Q: My A1 printer is visible in Bambu Studio but I cannot send files to print**
|
||||
A: StudioBridge only handles UDP discovery — the actual print job transfer is done entirely by Bambu Studio over MQTT (port 8883). If the printer appears but printing fails, follow these steps:
|
||||
1. On the A1 printer screen go to **Settings → Network** and enable **Only LAN Mode**.
|
||||
2. In Bambu Studio, open the **Devices** tab, right-click the A1 and choose **Log out**, then reconnect using the **LAN Access Code** shown on the printer screen under **Settings → Network → LAN Access Code**.
|
||||
3. Make sure Windows Firewall is not blocking Bambu Studio on TCP port **8883**.
|
||||
4. If the printer was connected to the Bambu cloud for a long time, log it out of the cloud and log back in — this refreshes the internal credentials ([Issue #12](https://github.com/Rdiger-36/StudioBridge/issues/12)).
|
||||
5. Try running StudioBridge with the `--direct` flag to send the discovery packet directly to Bambu Studio instead of broadcast:
|
||||
```
|
||||
.\StudioBridge.bat --direct
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
# Portable Launcher for StudioBridge
|
||||
|
||||
Binary file not shown.
@@ -1,3 +1,3 @@
|
||||
@echo off
|
||||
set "JAVA_HOME=%~dp0jre"
|
||||
"%JAVA_HOME%\bin\java.exe" -jar "%~dp0StudioBridge-2.1.1.jar" %*
|
||||
"%JAVA_HOME%\bin\java.exe" -jar "%~dp0StudioBridge-2.1.2.jar" %*
|
||||
Reference in New Issue
Block a user