Hi.
We have serveral UCCNC installations running on AXBB-E controllers. On one of them we suddently got the "ext. e-stop" alarm, resulting in the machine stopping. Its for a small desktop 2-axis CNC-machine performing a rivet operation with a pneumatic cylinder.
We increased the "debounce filter" to about 80ms but still got the same alarm.
Then to test, we removed the e-stop input setting completely in I/O-setup and set pin / port to 0 / 0, but still got the same alarm?! Should not the alarm be impossible to trigger if I have removed the emergency input signal all together, or can the alarm message "ext. e-stop triggered" come from other input noice other than only the emergency stop signal?
UCCNC version 1.2113
Firmware 1.0050
Hardware 1.0000
API version 2.1820
Standard Windows 10 desktop computers with dual ethernet cards (one for the controller and one for the local network)
No spindle, no plasma, no other noice-producing components.