P1S fails at 0% cloud download, LAN mode works

I’ve had a P1S for a few years and put about 500 hours of print time on it. When I first received it I ran it in standard cloud mode, but switched to LAN mode last year when the Authorization Control change happened. It’s been running fine in LAN mode, but I’ve just ordered an H2C and decided to go back to the cloud connection to simplify management of multiple printers. Unfortunately, I can’t send gcode to the printer, as the “downloading” progress bar never advances beyond 0% and eventually fails with a communication error.

So far, I have tried:

  • Updated Bambu Studio to 2.1.7.62
  • Updated printer to 01.10.00.00
  • Renamed printer
  • Logged out of printer and back in
  • Factory-reset printer
  • Added wireless AP a few feet from the printer
  • Reformatted SD card in printer
  • Confirmed SD card could be read/written in computer
  • Sent jobs from two computers and from Handy

None of the above steps made any difference; the printer still fails to download the gcode.

I put the printer back in LAN mode and connected with access code from the same computer and the same session of Bambu Studio, and it downloads just fine; there’s clearly not a networking issue. And there’s not a firewall rule or anything; I have an A1 Mini that prints just fine from the cloud on the same network.

Any ideas? Thanks!

Back in the day when you LAN only’ed it, did you setup rules on your router to block outbound? If so those might need to be undone.

Otherwise, I would factory reset the P1s, delete it from your bambu studio, relaunch bambustudio, and re-add from scratch in that order. I’m assuming you mean “as the “downloading” progress bar never advances beyond 0% and eventually fails with a communication error.” as this is all happening on the P1s and it’s screen, not in front of your PC [uploading issue vs downloading issue].

1 Like

Nope, I already double-checked that there were no blocks in the router.

Turns out I did have the printer blocked in the router. Embarrassing, since I had already checked once, but I had it blocked in a different setting that I had not checked.

Thanks for reviewing my problem!