First I have an MKS board. Sorry didn’t know about the problems until long after I had purchased it. Haven’t been able to get any help from them. Sent some emails to addressed I could find but no response. Only positive here I can post is I gave the board a bad review on amazon.
My problem:
I have all my endstops setup and wired up and they appear to be working. I can manually trigger them and see the result by running a M119 in the console. When I choose to home The printer will hit the endstops and grind away at the endstop for a few seconds until it stops and I have to reset my printer.
I have posted my full config here.
The pastbin code is: MTadz8X0
I have had a miserable time with this printer. I have yet to even get it to home correctly and haven’t even got it to print a thing. I have read over the website and tried every settings but they all seem to make no change. ANY help is much appreciated.
Imported from wikidot
First I have an MKS board. Sorry didn’t know about the problems until long after I had purchased it. Haven’t been able to get any help from them. Sent some emails to addressed I could find but no response. Only positive here I can post is I gave the board a bad review on amazon.
Thanks for contacting them first, that’s all we ask. They ( and not the project they are eating alive ) should be helping their users, and we want everyone to see that they don’t. Unfortunately it’s very common for users to realize the problem only after the purchase, not sure what to do about it …
About your problem : I’ve seen something similar happen when the user had the x endstop in the y connector and vice-versa. Printer hits an endstop but doesn’t stop because it’s not the right one. And M119 looks fine if you miss the problem. It’s likely not that, but check.
Appart from that, can you try reducing your homing speeds by a factor of ten ( just for testing ).
Also if that still doesn’t work, try uncommenting this line :
#endstop_debounce_ms 1 # Uncomment if you get noise on your endstops, default is 1 millisecond debounce
Well I wish I could say it was some massively complex issue. However in the end it was exactly what you listed. I had X and Y swapped. I had taken the board apart and plugged it back in twice wrong…
Thank you for the reply.