Layer shift for just one layer and then back again?
Any idea what could cause a layer shift in X only for one layer, and then go back to normal? VC4-300
Solution:Jump to solution
I had similar issue at the begining and it was solved by turning on Performence Mode when configuring the printer.
16 Replies
Hotend loose. It hits something and gets knocked to the side, then hits it again and is knocked back
Would the other walls be that well aligned if that were the case though?
This is a stretch but check g code. If that layer or the one directly below is substantially longer then it can cause something like that.
Hotend is fully tight
Nothing obvious.
I have also seen some layer shifts in other prints too, where it shifted in both X and Y. It seemed to shift back in one axis, but not in another.
I am also getting this clicking sound from the two lower rear idler assemblies, not quite sure what is going on there.
Some people have suggested bearings may be dodgy
Wondering if it's maybe related to this?
Maybe? I don't see any movement in those shafts, but it was a small shift
At one point I thought the clicking was because the grub screws were not against the flat of the shaft - it went away when I fixed that, but it's back now
And grub screws are still tight and against flat, so I think it maybe is a knackered bearing
it does kinda sound like that yeah
But would that really cause a layer shift?
I don't have any experience with a failed bearing. Maybe ask that specifically in general?
Ah, looks like I did not review slicer settings when I imported them into PrusaSlicer.
The acceleration values look high?
Mind you, I guess the print settings are overriding that
Those seem fine
New post started - seeing different thing now (Layer shift is not going back to start). Also think that it's the steppers skipping
https://discord.com/channels/582187371529764864/1298979475001970768
Solution
I had similar issue at the begining and it was solved by turning on Performence Mode when configuring the printer.
Yes, that was what turned out to be the issue
I was under the impression that one should get things generally working, and then enable it.