Quote Originally Posted by A_Camera View Post
I don't think it is a debouncing issue. I assume you are using NC type connection for your e-Stop, so in normal case you have a permanent connection. When you push the button you break the line and bouncing would mean the switch will make several contacts, but that would not make a difference since you should expect that UCCNC already detected the first break. That is what you normally want from an e-Stop. You should not have a button which needs debouncing in NC connection because the debouncing will only delay the button push detection circuit, which is pointless and counter productive in an emergency situation. But... if you have a bad contact somewhere in your e-Stop circuit and you have NC circuit then it may trigger the e-Stop function, which again is a good thing and you don't normally want to hide that because it indicates an error which should be fixed and not hidden.

So, if I were you I would NOT try to add any debouncing but would start a fault finding activity, checking every wire and of course, also the BOB. As a matter of fact, I would also try to use a different port of the UCX00 board you are using, because in theory, even that can fail. If nothing is connected except the BOB then you MUST also remove the logical connection in UCCNC so that the input is not defined as e-Stop. You can do that in the Configuration, I/O setup tab. If you have done that and still get e-Stop then I am lost and suggest you contact CNC Drive support. I don't know which UCCNC version you are using, perhaps if it is a test version there is a bug, they can check that out.
Thanks!

That's exactly what's confusing me.
Even when I reset the e-stops port and pin to 0/0 instead of pin 12 port 3 (in my case) I still get ext e stop.. weird!

Skickat från min SM-G955F via Tapatalk