I have made some more progress on this issue recently, although the end result is that the problem looks stranger still.
Yesterday, I completely re-lubed the system, re-aligned, re-tensioned, and sanded down the burrs/nibs off the y-axis rod, and the system rolled much smoother. I printed off a couple things and they turned out well, so I thought the problem might be fixed. To my disappointment, it was not.
The weird part is that the y-axis shift was completely repeatable in a certain part. It is best explained in order of events:
-I printed a test run with two "heatsink" looking parts. These parts have just a row of double-perimeter walls to easily detect y-axis shifts.
-The two heatsinks are arranged with one in the back of the platform, the other in the front.
-I examined them from the side, and found that the heatsink printed at the back had absolutely no y-shifts whatsoever. However, the one at the front had a multitude of seemingly random displacements.
-I repeated the same exact test and examined the parts again. Turns out, the exact same pattern of defects was duplicated on the "forward" heatsink part. The attached images show this.
What conclusions can I draw from this, or what causes can I eliminate?
-It cannot be slipping of the set screws or pulleys. It seems impossible that they would randomly repeat the exact same slippage and correct themselves when they go to one side of the stage.
-It has nothing to do with belt tension. The two heatsink tests were conducted with very different settings of belt tension and still yielded an identical result.
I am growing increasingly suspicious of firmware or software issues, at this point. One thing to note is that when I fixed my extruder, I uploaded marlin again with a different thermistor code. However, I don't know if it is the same marlin version that I was using previously. It says Lawsy's in the code, I think. More importantly than what version I am using, what could the firmware do to cause this?
Could it be something like the steps_per_distance for y-axis is incorrect now, maybe? So perhaps it discretizes it incorrectly when processing g-code?
Thanks for the help, everyone. I think I am making some progress, at least...
Post's attachmentsheatsink bad.jpg
heatsink bad.jpg 1.57 mb, file has never been downloaded.
heatsink good.jpg
heatsink good.jpg 1.57 mb, file has never been downloaded.
You don't have the permssions to download the attachments of this post.