The P1S stays offline in Bambu Studio or never joins the network, so you cannot start, monitor, or pull logs from a print even though the printer itself powers on.
Most P1S link loss is configuration, not hardware. The table lists the connection faults we resolve remotely most often and the first thing to confirm for each.
| Cause | Likelihood | First Check |
|---|---|---|
| Wi-Fi is 5GHz-only and the P1S needs 2.4GHz | High | Confirm the router broadcasts a 2.4GHz SSID the printer can see during setup |
| Wrong network or credential after a router change | High | Re-run binding in Bambu Studio and verify the SSID and password entered |
| Printer stuck in AP mode and never joins the LAN | Medium | Check whether the hotspot SSID is still broadcast; if so it did not complete binding |
| Firmware mismatch between printer and Studio | Medium | Compare the printer firmware version to the Studio version and note any update prompt |
| LAN mode or cloud account binding conflict | Low–Medium | Check LAN-only mode and whether the device is bound to another account |
Work through these in order. Every step is something you can do from the slicer or the printer screen without opening the case.
The P1S connects on 2.4GHz only. Verify your router exposes a 2.4GHz network and that the SSID you pick during setup is not the 5GHz one.
If the printer still broadcasts its own hotspot, binding never finished. Join that AP from your phone and complete the Wi-Fi binding so it joins your LAN.
Remove the old device entry and rebind with the current SSID and password. A router swap or password change is the usual hidden cause.
Compare the printer firmware version with the Bambu Studio version. A mismatch blocks the handshake; we tell you which side to update and in what order.
From Studio or the printer, pull the network and binding log. We read it to confirm whether the failure is association, credential, or cloud binding.
A P1S that will not connect is almost always a link-layer problem — band, credential, or binding — rather than a dead Wi-Fi module. The fast tell is whether the printer still broadcasts its own AP: if it does, setup did not complete; if it joined the network but Studio cannot see it, the issue is firmware or account binding. Both are resolvable from the slicer.
For the wider context, see No connection / offline device and Wi-Fi & LAN device binding. On the same family, Bambu Lab X1 Carbon — HMS Error Codes covers faults that look like disconnects but are really subsystem errors, and Bambu Lab X1 Carbon — Not Extruding is the next step once the link is back.
Send the binding log and we confirm the exact failure point. Because this is software and configuration, most P1S link loss is addressed without touching the hardware.
Send the binding or network log and your Studio version. We pinpoint the band, credential, or firmware cause remotely so you reconnect without a service call.
Submit Your Case Connect With SpecialistsWe do not perform hardware repair, we do not replace parts, and we cannot promise a 100% resolution. Our role is limited to remote diagnostic and step-by-step guidance based on the information, photos and logs you share.
Usually the network is 5GHz-only, the SSID or password changed after a router swap, or binding never completed so the printer still sits in AP mode. We confirm which from your log.
It connects on 2.4GHz only. If your router merges bands under one name, pick the 2.4GHz SSID explicitly during setup so the printer can associate.
That points to a firmware or account-binding mismatch rather than Wi-Fi. We compare the printer and Studio versions and walk the rebind so Studio discovers it again.
Almost never. Link loss on the P1S is overwhelmingly band, credential, or firmware. We only suspect the radio after the logs rule those out, and we confirm that with you first.
Faults that mimic a disconnect but are subsystem errors.
What to check once the link is back and printing.
The AMS-side fault that often pairs with a lost link.