I’ve seen some other posts which mention this problem I’m having, but nothing with a definitive solution so I’m starting a new thread to add my details, in the hopes that it’ll help someone in the future.
Problem: Despite my S3 having worked fine the previous day, upon powering on and hitting the Initialize Machine button, the X-axis motor is emitting a loud racket and moving the toolhead left and right short distances very rapidly (like a mm or two either direction). The Y and Z axes are fine.
About 6 months ago, the machine exhibited this X-axis jitter/stutter behavior for some time (days) and then it went back to behaving normally, as suddenly and magically as the stutter appeared. I haven’t used the machine much in the past 6 months but over the past couple of days got the machine set up for a new project and now the jitter state is back and it doesn’t seem to want to leave.
Things I’ve discovered:
powered-off, the X axis moves easily and smoothly.
I have a spare Carbide3d motor. Plugging that motor to the connector near the toolhead (ie, on the other side of the long cable from the controller board) results in the jittery/stutter-y movement and lots of vibration of the motor.
Plugging the spare motor directly to the controller/Grbl board (no long cable) yields a smoothly moving motor.
Progress! So, now I’m looking at the cable as the culprit and I’m thinking that perhaps over time, one of the wires has degraded because of the many bending cycles. That could also explain why this behavior is intermittent, if the wires are degraded but not totally separated. All that said, it just doesn’t seem very high probability. Why does it work so repeatably when it’s working, before it magically flips to the “bad” state, where it’s equally repeatably bad until it suddenly flips states again?
I pulled the X-motor cable out and inspected it and visually it’s fine but of course I’m going to replace it. While I wait for a replacement cable to try it out, is there something else I should be looking at?
I’m hoping someone has seen this behavior before and can save me some time!
thanks all -