Ext e-stop triggered

[BJB]

Wonder if anyone can help me. I have recently been getting a lot of "Ext e-stop triggered" messages. After looking on the forum I saw a post that said disabling the e-stop trigger would solve this problem. I couldn't find where to disable it.
So I changed the the e-stop pin on the I/O setup page from 11 to 10. This seems to have been solved the problem. Is it OK to leave like this?
Just for info, I'm using a Stepcraft M-1000
Thanks for any advice

[BJB]

Just found out that if I leave it on pin10, I cant use the tool length sensor, so changed it to 0 is that ok to leave it at that?

Thanks

[fsli]

I'm not familiar with the Stepcraft M-1000, but if it has an actual emergency stop button then I'd question the wisdom of disabling the input pin. You will lose the ability to stop the machine in a true emergency.

Looking at the Stepcraft web site, there is a mention of axis position encoders which will trigger the emergency stop if they get out of sync with the commanded axis movement. If that's what's happening, then you should be looking at why the axis is losing steps. Did you change the velocity and/or acceleration parameters?

I can't help but think these questions are better suited to Stepcraft support, or some Stepcraft-specific forum.

[BJB]

didnt change anything I'm aware of, but will get hold of Stepcraft to enquire.
Thanks for the advise

[Siharrison]

Hello did you get an answer for this as I have the same problem
Thanks

[RsX]

try the "input signals debounce (ms)" feature in the settings
I used 3ms for inputs