Hi,
no I don't think so. Snap action microswitches are correct for home switches and proximity switches for limit switches. The simplest way to solve your problem is to have
three individual home switches, one for each axis and ideally each with its own input pin and separate limit switches. Note that all your home switches need
to be 'inside' your limits. Then you can reference (home) your machine without any of the limit switches triggering. With your motion controller a 57CNC
you have swags of IO, why are you trying to economise on inputs? Faults like the one you have described are exactly the sort of thing that occurs when you try
to do double duty with your switches.

Craig

IMHO i cannot see a problem with proximity switches as home switches and limit, i have used these on my machine for 4 years as the same and will do on my new machine shortly, they are very accurate.

DazTheGas

I got a tip to solve this by adjusting the “Debounce interval” and “Index debounce” settings. unfortunately in  mach3. I could not found this function in mach4. Does it exist in mach4?

Hi,
those are settings in your motion controller plugin not Mach.

Craig

OK. Thanks Craig. I will have a closer look to the board doc.