Post
by Sodium100mg » Wed Mar 11, 2020 2:44 am
Have you tried upgrading firmware? There is no bigger waste of time than trying to fix a problem that has already been fixed.
I'd test the Z screw. Things move simultaneous, so a binding on the Z could be reflected in the X. Unlock the motors and turn the Z up and down. Then use the jog to run the screw all the way up and down, listen for any noises. Clean it. Look at the bearings on the far side and tighten the whole structure. check the bearings are tight.
Swap motors around and see if the problem shifts axis.
On the side of the lower portion of the box, look for a dent when the nozzle impacted the side of the box causing the missed steps. Or is there any bit of filament floating around in the belts that is causing the problem. With how good everything else looks, it shouldn't be a loose belt. You said you re-leveled the bed, also make sure it is tight and you have good adhesion between the bed and the print.
I can't imagine a gcode error that could cause it, other than the z-hop issue others have mentioned that newer firmware might help. I'm guessing the z-hop on landing can pound in like a tent stake and cause side motion issues, when combined with other variables.
Setup your camera to take a video and watch what happened. Set the frame rate low.
I don't want to sound like an octoprint salesman (octoprint is free), but it sure is nice to have a log file (and timelaps) to look back on and see what happened, rather than guess. If the problem is a motor error, there will be nothing logged.
The speed you are running seems slow, not that it should be a problem, just that you are not pushing the motor limits. I'm running at 100m/s and would not be surprised if I saw crazy stuff.
