Bambu Studio forgets printer and shows 'no printer' at next startup

davinciano · September 25, 2024, 8:57pm

I recently switched my Bambu A1 printer to LAN Only mode but now Bambu Studio is giving me problems.

When I add the printer in Bambu Studio (using Access Code from the printer) then it works fine, but only until I close Bambu Studio.

When I later start Bambu Studio again, it has forgotten about the printer and shows “no printer”.

I must then first reconnect the printer in Studio again, which requires me to enter the Access Code again. This is getting increasingly annoying and provides a bad user experience each time again.

This appears to be a bug. Please fix it.

lulezi · December 14, 2024, 3:11pm

I have the same issue with my X1C. Also using LAN Only mode.

lkraus · December 14, 2024, 3:44pm

This seems to help:

This is possible to achieve on the latest version 1.9.3.50, at least on Windows:

Open Bambu Studio, go to Device, No Printer, and select your LAN only printer. Input its access code and make sure you can connect to it. Afterwards, close Bambu Studio.

Navigate to the following file:

“C:\Users\AppData\Roaming\BambuStudio\BambuStudio.conf”

Edit this file and search for “user_access_code”

You will find something like this:
"user_access_code": {
    "<PRINTER_ID>": "<ACCESS_CODE>"
}
Now, change the name of the field to just “access_code”, like this:
"access_code": {
    "<PRINTER_ID>": "<ACCESS_CODE>"
}
Save the file. Now, Bambu Studio will remember your printer’s access code each time it boots up.

In LAN only mode, I still get “No Printer”, but at least the printer is still listed in the dropdown and the access code does not need to be re-entered.

lkraus · February 3, 2025, 11:54am

An OrcaSlicer fix for this problem of a “forgotten” LAN-only printer seems to have been found, and is awaiting approval for merging with v2.3.0-dev. It also fixes binding to a printer in a different subnet.

More info here:

github.com/SoftFever/OrcaSlicer

Proper support of Bambu LAN printers

SoftFever:main ← Noisyfox:dev/save-local-machine

opened 11:22AM - 31 Jan 25 UTC

Noisyfox

+249 -59

**The latest download link can be found from the "Checks" tab above or [here](ht…tps://github.com/SoftFever/OrcaSlicer/pull/8256/checks). There should be an "artifact" dropdown on top of that page once the build is completed.** This PR solves the following problems: - Bind printers in different subnet - Binded LAN printers are not automatically connected when switching to Device tab ![32217e0ea2ed5434d8916ad5c46e69c4](https://github.com/user-attachments/assets/a9189d74-c9b4-466c-9839-15cb79cf89bc) ![2fc422ddd3a89ae675de426953e44c1b](https://github.com/user-attachments/assets/2768c46c-c992-46a5-bb32-caa3aacfa62b) ![image](https://github.com/user-attachments/assets/0a65fffa-401a-4aa4-ba46-7681b642f1d1) Few improtant things to know: The automatic printer info detection (ie, the step in the first image) doesn't work on MacOS, when you click "Connect" you will immediately be prompted to the second image to enter the printer details. (I don't know why but Bambu does not provide this capability on MacOS for their network plugin) AFAIK, P1 series do not support automatic printer info detection (as tested by @SoftFever and myself), so the first step is gauranteed to fail, which is unfortunate but expected. Simply click the "Manual Setup" button (which will appear after clicking the "Connect" button then wait for a while) and enter the printer detail and you should be good to go. If anything entered wrong, you could simply unbind the printer and do it all over again. I know current binding flow is not very user-friendly, but consider how rare this will be used, I think it's OK. Given the current situation this is the best I could do with the closed-source Bambu network plugin. I only have a P1 so I couldn't throughly test this PR. Please if you have different printers and home network configurations, your feedback are valuable to help validating and improving this PR, thanks in advance! Fix #6169 Fix #8097

Use at your own risk, since it is not yet really even a nightly beta release, but my X1C has been found on startup for the past three days.

user_1991575452 · February 7, 2025, 8:57pm

I have the same problem on my X1E. Had everything working fine for over a year and now I cannot connect LAN only mode. Happened after I updated firmware. Tried to go back to previous firmware and no luck.

lkraus · March 27, 2025, 5:00pm

Updating my earlier post, my LAN-only X1C has not been “forgotten” by OrcaSlicer since Noisyfox made the change in beta January 31. That change is now a part of the OrcaSlicer V2.3.0 Official Release.

No need to keep entering an access code, no need to re-select a printer, it is always ready to print.

However, Studio 1.10 and 2.0 both continue to say “No Printer” until I select the printer again.

Kzneft · September 22, 2025, 12:55am

Same problem looks like I have. Was using Lan, but of course you can’t see your X1C on your phone unless you are “binded” with the printer, so I bound using Access code and all was good. Turned off printer, and when I turned back on Bamboo studio says it can’t find printer, even though my phone app says “online”. Only choice now in Studio is “bind with code” or “bind with access code”. I try access code again and it says “The printer has already been bound”. So now what? Studio still says it can’t see the printer???

Kzneft · September 22, 2025, 12:59am

Gave up and went back to LAN only.

JonRaymond · September 22, 2025, 1:12am

Check to see if you are logged into the same account in Bambu Studio that you bound the printer to. It seem to be a common mistake people make.

Kzneft · September 22, 2025, 6:33pm

Tried it again. Turned off LAN Only mode, Scanned the QR code with phone and it found it. I can see everything about the printer from my phone. Now trying to connect to Bambo Studio (PC) with Access Code, press connect and get the error “The printer has already been bound”, but Studio still says No Printer found. My Studio is the same account I originally used. I did log out and log back in. Still no change.