X-axis position-error since 3.7.2
Today is the second time since I installed this firmware-version that my MK3S lost the positioning on the x-axis after a stopped print. That's especially annoying since it pushes the PINDA over the edge of the bed, initiates self-calibration and then -since the PINDA isn't over the bed- rams the nozzle into the bed. First time this happened I could just watch from the distance as my printer ruined a steel-sheet, this time I jumped to the reset-button just in time.
The kit worked perfectly before this update and I never had an issue with it. It even printed better surfaces than the industrial printer at the company I work at.
Anyone else having the same problem or a solution?
RE: X-axis position-error since 3.7.2
Coincidence ... you are most likely having friction problems on an axis. Y is sticking, or X is sticking. Look at the crash detections to find which is causing the issue. (or if using Octoprint, disconnect the USB cord and try printing from the SD card).
RE: X-axis position-error since 3.7.2
I'm not using octoprint, I'm just using the cable for the firmware-update. I'll re-check the crash-detection once I finish the next recalibration. I would be surprised if it's something with the axis. I double-checked them all after I had a little too much slack on the Y-belt after first assembly when I got the kit 3 months ago. I also have no artifacts in the prints that suggest sticking of an axis, at least not since I adjusted the belt.
RE: X-axis position-error since 3.7.2
Just had the same occurance again: No crash-detections registered.
RE: X-axis position-error since 3.7.2
Leaving the USB cable is invites problems. There have been a couple of reports of random resets just bumping the cable.
Prusa has been known to "experiment" with drive currents version to version and let users alpha-test the change. You might try reverting to 3.7.1 and compare against 3.7.2. Just to make sure it is firmware. If the issue goes away, stop fighting it and live with 3.7.1.