Hi all,
a strange thing happened to me with my P1s which is one year old and has 900 hours of work. I downloaded this model of stand for the PS5 controller from makerworld. For time reasons, I decided to cut the model into two pieces as shown in the attached photo and I printed plate number 1… All ok. Then I took the model that is on plate 2 and decided to cut it again, to have a total of three pieces, and at this point I went to print plate number 2… At first everything was fine but then after about 11mm in Z the printed model, the print head starts and hits the front right corner of the printer just as if it wanted to do a Homing and the X and Y axis motors started to make a terrible noise like “trrrrrrrrr”. Luckily I was nearby and so I immediately turned off the printer with the switch on the back and at this point the questions, Was something damaged? Why did this happen? On the PC simulating the gcode nothing abnormal is seen. Could the cause be that I cut a model that had already been cut once?
I did it all with Bambustudio.
There is a chance that your SD card had a read error and on the P1S that can cause some wonky issues. Recommend getting a new SD card.
Regarding if this caused damage, likely not as long as the nozzle tip did not collide with anything during that move. The rattling noise itself comes from the servos loosing steps but that on itself usually does not result in damage.
Thank you very much for your reply,
I changed the original microSD two or three months ago, with this one in the photo that I attach.
Normally I format it with a program called (HDD Low Level Format Tool) that does low-level formatting.
Then after inserting it into the printer I format it directly from the printer (to be sure that it is formatted in the correct format)
In your opinion, do I have to change it again?
In your opinion, can we rule out a problem with BambuStudio because I cut a model that had already been cut previously?
Luckily the tip of the nozzle did not touch anything in Z… at a certain point there was only the X and Y movement that caused the ToolHead to hit the front right corner.
PS: when I do the total calibration of the printer, are the detected data saved on the MicroSD? If I format the microSD do I have to redo the total calibration?
Thanks and sorry for the many questions…
Have you run it through a calibration post-crash? If not, I would do that first.
What do you mean by on PC simulating G-Code? Maybe just a terminology thing but never heard that phrase before.
Not everything is shown by default in Bambu Studio and I think travel moves are one of those unchecked items. You might want to enable it and then go layer by layer in studio to see if some unexpected move takes place.
As an owner of a P1S I can say that mine will occasionally fault out for no apparent reason, rare but it does happen.
Also, the most recent person to have done something to model prior to you uploading may have put some odd setting in that is incompatible with your printer.
Yes, I did a total post-crash calibration, and then I tried to print a BambuCube 30x30x30mm and everything went well.
With “Pc simulate Gcode” I meant that I tried to simulate the printer’s movements in Bambustudio with “travel movement” turned on but I didn’t find anything abnormal…
Before starting the print I checked to select P1s as the machine and I set my custom work profile for a layer height of 0.2mm. (as I always do every time I download a model from makerworld)
and then the problem occurred after it printed up to a height of 11mm in Z
Do you think it could be because I cut a model again that had already been cut once before?
I still wanted to add…
from Bambustudio after making the slice, I clicked on the button at the top right with the words “PRINT”
If instead I had selected the “SEND” option would it have been the same thing?
I mean, in both cases the Gcode file would have passed through the bambulab Cloud before arriving at the printer?
Could the Gcode file have been corrupted during this transfer, or is this thought of mine just science fiction?
Personally I prefer Sandisk. They’ve been around more or less the longest and I’ve not had issues with any of them.
Sandisk is generally regarded as being more reliable. Google sandisk vs Lexar and you’ll see what I mean.
I thank you for your contribution…
I hope to be able to find a solution to ensure that a similar event that could damage my printer never happens again.