Open kk7ds opened 2 months ago
Same behaviour on P1S
Same behavior on A1 (01.03.00.00)
OMG I thought it was just me.. My P1S does the same thing.
I've gone back to 1.9.1 and it all works fine.
Same on my X1C with 2.1.1, Win11
Same issue on my X1C also with v2.1.1, Win11
I'm having the same issue, Orca Slicer 2.1.1, Windows 11. Uploads from slicer when pressing "Print Plate" have also slowed to a crawl - seemed to start at the same time. Sometimes the massive delay in uploading means the transfer fails.
When it does succeed, after taking 10-15 minutes to transfer a 3-5MB file for printing, the system consistently disconnects at the point where it switches to the "Device" tab. I have to reconnect (by reentering the access number) at that point, though the print starts successfully.
Same here. Orca 2.1.1, MacOS 14.5 M1, X1C
I'm having the same issue, Orca Slicer 2.1.1, Windows 11. Uploads from slicer when pressing "Print Plate" have also slowed to a crawl - seemed to start at the same time. Sometimes the massive delay in uploading means the transfer fails.
When it does succeed, after taking 10-15 minutes to transfer a 3-5MB file for printing, the system consistently disconnects at the point where it switches to the "Device" tab. I have to reconnect (by reentering the access number) at that point, though the print starts successfully.
So... as far as I know I have changed absolutely nothing in my setup, but this has stopped happening. 🤷
It occasionally doesn't happen for me. I'd say give it time :)
Same for me. A1 Mini, Orca 2.1.1, MacOS 13.4.1.
What does "give it time" mean? It will randomly not require the code, but it's less than 1 in 5 times connecting, at best. I've tried to figure out what makes the code stick, to no avail. I can have my machine connect to watch a print, bring something else into the foreground for a while, and have to enter the code again. Quite frustrating.
@HodGreeley I said that because @Zalatra said it seemed to have "stopped happening". My point was "give it time, and I'm sure it will start happening again". Like you, it sometimes works as expected, but almost all of the time does not. I think @Zalatra was just experiencing one of those occasional works as expected spurts, so I was encouraging them not to think it had fixed itself.
Sam issue here. I used to experience this from time to time, but since updating to 2.1.1 it happens every single time my computer is brought out of sleep.
On my Windows machine, setting "Network Profile Type" to "Private network" resolved my issue of the passcode being forgotten since updating to 2.1.1. I haven't found a solution for my Mac yet. YMMV
+1
The workaround for this is to get all your bambu printers connected in Orca, close Orca. Open your OrcaSlicer.conf
(~/Library/Application Support/OrcaSlicer/OrcaSlicer.conf
on macOS), find the "user_access_code"
section, and update it to be just "access_code"
, save & close. Open Orca again, congratulations 🎉 , it won't forget your printers again.
Really this seems like a bug in the bambu network plugin more so than Orca, as the same failure is present in BS.
It definitely is a bug in the plugin because it started happening with studio as well. It definitely seems like something Orca should be able to override, as even before this my printer would occasionally be forgotten.
Anyway, I don't have that section in my config at all:
$ grep access ~/Library/Application\ Support/OrcaSlicer/OrcaSlicer.conf
$
Can you show me what it should look like so I can add it?
@katherine-black fix works for me. Conf file section looks like
"access_code": { "serial number": "code" },
Replace serial number with the hex serial number you can find under Device > Update. Code is your 8 digit access code.
@katherine-black @HodGreeley This doesn't seem to work for me. I had no "access_code" section to copy. If I add a top-level key like you show, then start Orca, it doesn't see my printer as a "known" one, and when I click on it, it still prompts for the password. After exiting Orca, the config change I made is still there, but sorted in a different place (so it must have been read in and written back out).
The workaround for this is to get all your bambu printers connected in Orca, close Orca. Open your
OrcaSlicer.conf
(~/Library/Application Support/OrcaSlicer/OrcaSlicer.conf
on macOS), find the"user_access_code"
section, and update it to be just"access_code"
, save & close. Open Orca again, congratulations 🎉 , it won't forget your printers again.Really this seems like a bug in the bambu network plugin more so than Orca, as the same failure is present in BS.
This worked for me too
I was eventually able to get it working by putting it in the config, starting orca, selected the printer, put in the code when prompted, then exiting.. Seemed like just putting it in the config was not enough, I had to have it there and then exit orca while that was selected as the active printer or something. After that, it seems to stick now.
Anyway, hopefully Bambu will fix this properly.
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1
Operating System (OS)
macOS
OS Version
Sonoma 14.5 (latest)
Additional system information
Macbook Pro M1
Printer
Bambu X1C (in LAN-only mode)
How to reproduce
Actual results
Printer constantly goes to the unknown list requiring the access code when connecting.
Expected results
Remember the access code. This worked fine before I updated to 2.1.1, continues to work fine in Bambu studio on the same machine with the same printer.
Project file & Debug log uploads
No project file required. Can reproduce just while monitoring an existing print. Very frustrating during a multi-hour print that every time I wake the machine or go back into orca to check on the print, I have to dig out the access code again.
Checklist of files to include
Anything else?
No response