Not sure if it’s connected, but wifi signal seems to alternate from good to bad sometimes. Always full and sometimes kinda loses bars and sometimes Bambu Studio even says connection lost, but seems to recover almost instantly.
Figured the glitch by the light also. I have light turned off and after the bug occuring it’s turned on again.
Got a new sd card, opened android Handy app, Bambu Studio and then all these simultaneously, but couldn’t repeat that stopping by myself, it’s just happening when it’s happening.
I left the sound on on my A1, and yesterday I heard it make the boot up sound multiple times when idle. Usually there was a couple hours between each time. The A1 and P1S also stopped mid print yesterday just as I was checking on them.
Everything is up to date.
Idle AND midprint.
cloud connected.
Live view is generally active for P1S but I don’t remember if it was at that moment.
Using both Studio and Handy, but sending print files via Studio.
I’ve been having this same issue for a couple of days now, I already upgraded the SD card to a high quality one from day one, I disabled time-lapse as well before this issue ever occurred. I just recently disabled “videos” from the “record settings” on the app. I noticed “auto-recover from step loss” is turned on, leaving it on for now.
When the printer senses step loss it will rehome the print head and continue printing. This shouldn’t be related to the “Stopping while printing” issue that many users are experiencing.
Same here, p1s with ams. Issue started after upgrading to the latest firmware few days ago, observed it on 40minute print today.
Chamber led goes off, print pauses, display goes off. After 20-30 seconds the print resumes as if nothing happened.
First things first, yes, the Panda Touch is plugged into the USB plug on the mainboard (I’ve had it for about a month now). On the 24th my P1S paused about 1 hour into a 1.5 hr. print, and then resumed. I did not notice the lights or display going off. On the 25th at 1.5 hrs. into a 3.5 hr. print both the lights and display went off and back on. I don’t know how many other folks have a Panda Touch on their machines, but this issue seems pretty widespread for it to be that. I’m keeping an open mind though, I spent 30+ years at Cape Canaveral AFS and that taught me too never jump to conclusions about what a problem “might be”. My symptoms are very similar if not identical to what others have reported, and started after the most recent update.
Also wanted to add:
Printer model: P1S
AMS: Yes
Cloud connection: On
Live view: Off
Slicer used: Bambu Studio version 1.9.3.50
Print sent through Bambu Studio version 1.9.3.50
This started happening yesterday (that I noticed) for me too. Mid-print; I haven’t seen it do it in idle. As far as I’ve registered, this started happening after updating Bambu Studio to 1.9.3.50.
Printer model: P1S
AMS: No
Cloud connection: On
Live view: Off
Slicer used: Bambu Studio version 1.9.3.50
Print sent through Bambu Studio version 1.9.3.50
Wifi signal: 3 out of 4, often 4 out of 4.
Power grid is very steady; I run a server at home on the same fuse group as the printer, and therefore have monitoring for the current on the entire group. No issues here - and the printer’s power plug is fine, and other equipment sharing the same outlet are not affected.
Printer config:
Stock everything
10W LED-strip added through the USB-connection on the top of the printer
Fault description:
All lights go out, and the printer reboots. This takes around 10-20 seconds, then it resumes as if nothing happened. Nozzle doesn’t raise from bed prior to the reboot/pause.
As this has only happened twice in total for me (that I’ve noticed) over the last 2 days, I can’t say more than this at this point in time. During the same period, I have around 11 hours of printing different parts, with no issues other than the 2 mentioned here.
I doubt that this is panda touch related. Sounds like the machine PSU cut out which cut power to the AP board and the touch. I’ve seen this happening on many units without anything plugged into the USB port as well as A1 units.
To clarify, the printer is completely stock, no add ons, firmware is the current latest non-beta, as is the bambu slicer, connected via WiFi, the issue happens both when the slicer is on the device page and also when the computer is turned off. I have a feeling that it happens more often when the printer is connected to the latest version of the bambu mobile iOS app without the camera enabled.
This is speculation for a root cause but I observed that it started once the slicer and firmware were updated to the newest version
No problem with my P1S’s my two A1 minis were displayig some odd behavior however with stopping and then the screen refreshing midprint then continueing on to finish the print with no problems
I have 2 P1Ss both with identical hardware and firmware setups including the panda touch. One of them since the firmware update to 1.06 has been rebooting itself. I first realized something was wrong because I would come home and see my light had turned off in the chamber. This happened during a week when my printers were idle.
Two nights ago I ran the calibration cycles on both printers and left the room, when I returned an hour later the one printer said “ready to print” on the screen and the chamber light was off, the other printer said “calibration successful” and the light was on so I knew something was wrong.
I printed the same project on both last night, and they completed no issue but that’s the first print I’ve run since noticing the reboot has been happening.
My problem, at least from what I’ve observed, is the “pauses” are happening days apart i.e. one on Mon, one on Tue, nothing all day Wed, that I can’t be sure any one “fix” is the solution. If the reboot commands (if that’s what this is) are coming from the servers (I don’t even know if they have that capability) then going to Lan Mode would shield you from that. I have a feeling that this is firmware related, we’ll have to see how this plays out. I replaced my SD card just in case (I ordered it a couple days ago when everyone thought it was failing SD cards).
