MK4 X and Y axes can't find Home
I'm having a sporadic problem with the X and Y axes being unable to find "home". They, especially the Y axis, will repeatedly slam into the stops until they claim a collision or until they recognize home. My MK4 is in an enclosure but I've ensured there's no binding or impediments to X and Y travel. It's not unusual for the print bed to slam into the back stops more than a dozen times before it finally recognizes home.
Any ideas on the cause or suggestions for fixing this? TIA for your time and help.
Best Answer by ScottW:
A *lot* of people are experiencing this, and there are several threads here discussing it. One of the largest discussions is in the "Input Shaper" section, though it has proven to not be limited to Input Shaper firmware (it happens in the production released firmware as well):
https://forum.prusa3d.com/forum/postid/666533/
In my experience, it is pretty random. It will work fine for days, then start crashing into the stops and reporting collision the next day. Then it will be fine again. I haven't been able to pin down a relationship to anything else. Some people have had some success (an improvement, if not elimination) by tweaking belt tension. Take a look at that thread, some of the posts there may help.
RE:
A *lot* of people are experiencing this, and there are several threads here discussing it. One of the largest discussions is in the "Input Shaper" section, though it has proven to not be limited to Input Shaper firmware (it happens in the production released firmware as well):
https://forum.prusa3d.com/forum/postid/666533/
In my experience, it is pretty random. It will work fine for days, then start crashing into the stops and reporting collision the next day. Then it will be fine again. I haven't been able to pin down a relationship to anything else. Some people have had some success (an improvement, if not elimination) by tweaking belt tension. Take a look at that thread, some of the posts there may help.
RE: MK4 X and Y axes can't find Home
Ah, OK. Thanks for the info. I didn't look in "Input Shaper" or other feature-specific posts.