Find home fails (x-axis only)

[farmbotatunishanoi]

Hi,
After two years of no issues, the ‘find home’ button fails. Our farmbot (Genesis v1.6) finds home for the y and z axis perfectly fine. For the x-axis, it moves to the home position, slows down just before getting there, stops at the stop, moves out a bit and … moves back towards home, bumps into the stop again, but this time motors keep running … Giving us an e-stop as the only option. Both the encoder and motor x position keep moving into the negative until e-stop.

We have played with some settings, (using encoders/not using them, resetting x-position to 0, not allowing negative values for x etc) but the behaviour seems to persist through all of it.

I have checked cable connections and all seems good.

Perhaps anyone can give a tip on how to troubleshoot this furtrher

[farmbotatunishanoi]

Please let me know if I have published this question in the wrong category

[Ascend]

Hey @farmbotatunishanoi,

the category is fine, thanks for posting this in the right spot as this helps to keep the forum tidy.
For your issue, can you see if the motor is actually slightly turning when bumping into the endstop? I’m wondering if the belt is too loose and the motor is still able to turn at this point. Its weird that you can see your encoder value changing as it should stay almost the same. There is a given amount of motor steps to be missed until the motor is detected to stall. You could check if that value is too high (The FarmBot Web App) I think this should be around 5 maybe?

Let us know if you made any progress on that

[mvillion]

I had this error myself once - I think - It was kinda weird.

My X axis had gone into the negative values which caused it to think that the end stop was where it is not.

Are you able to do some simple tests?

Using the web interface, does X work normally when asking it to move in the direction you want - say from 500 to 10000 and back again?