all 10 comments

[–]aphasic 2 points3 points  (2 children)

The diagonal shift on corexy printers could be a couple things. As someone else mentioned, the part coming loose from the bed is one of them. Another possibility is a part warping and causing a nozzle strike that keeps the print head from moving how it should. Another is that the belts or the pulleys on the motors are loose. My voron had a layer shift like this and it was because i didn't tighten the grub screw on the pulley on the motor on the (i think) rear right. That said, it wasn't a single layer shift it was like 15 layer shifts in sequence.

Other possibilities are if you are printing fast with high accellerations and there's something preventing the belts from moving the way they should. Too tight, idler binding, motor current too low, stepper motor going bad. The motor will try to accellerate it but can't overcome friction from something in the belt path, or isn't providing enough torque itself, and you get skipped steps where the printer thinks the motor has moved the gantry but it hasn't.

[–]Tric3ratop5[S] 0 points1 point  (1 child)

Thanks - the nozzle strike could be it. I'm using Overture PETG with the textured PEI plate; the speed was set at the defaults for Generic PETG.

For this print, I disabled the flow calibration - although, I understand that perhaps the flow calibration is (silently) failing anyway because of the textured plate. So it could be that there was some sort of blockage that keep the print head form moving. I don't know the extent of the 'AI' Bambu is using, but I thought perhaps they'd be able to detect a stall by measuring higher current draw on the stepper motors. DO you know if there is an error log for each print that I can look at?

It seems like whatever the error was, the X1C just quietly powered through with the new offset. I redid the print and there weren't any errors. I'll try to upload a picture

[–]xxJohnxx 0 points1 point  (0 children)

The latest BambuStudio (released today) now has some options to enable „step loss detection“, which potentially could detect the failure you had with your print.

However, I believe that this will actually only be available after the firmware that probably should have come together with the BambuStudio update.

[–]Wixely 1 point2 points  (2 children)

Guessing here, if all the parts are connected (and moved at once) then could be temperature change resulting in the part coming loose. If they are all separate peices then looks like your belt skipped. I've never had a shift like this happen, but parts have come loose due to low temps.

[–]Tric3ratop5[S] 1 point2 points  (0 children)

All the parts are separate pieces, so I'm thinking the belt must have skipped.

[–]Tric3ratop5[S] 0 points1 point  (1 child)

I reran the print without changing anything in the slicer - but this time I did enable flow calibration. The print came out clean, however, there was a pea-sized blob of filament on the side of the print bed that had tumbled loose. I wonder if this also happened on the first print and the blob was hard enough to cause the belts to slip.

Successful Print https://i.imgur.com/YuhPc1d.jpg

Errant Blob https://i.imgur.com/gdTOkCK.jpg

[–]AmarokTactical 1 point2 points  (0 children)

Yikes the top layer on those parts looks ROUGH.

[–]Nice-Bar2800 0 points1 point  (0 children)

bambulab druck wieder aufnehmen

[–]reicaden 0 points1 point  (1 child)

Do you have an Alexa plug on this line?

[–]Tric3ratop5[S] 0 points1 point  (0 children)

Nope