KM_Axis.EStop vs. C Disable Axes

[SamMarrocco]

I'm currently using a KFlop thread that watches for the state of an Abort button/pin, that when closed triggers a DisableAxis() for every one of my axes.

I have a software UI button for Abort, that when clicked fires off a KM_Axis.EStop method for every one of my axes. I've noticed in the docs that the EStop method "stops the current motion and disabled the axis". Is the "stopping of the current motion" something I should be doing when I disable the axes in a thread (such as an Interpreter Halt?), or are these both doing the same thing?

[TomKerekes]

Hi Sam,

Actually commanding an axis to stop and then immediately disabling the axis shouldn't be significantly different than simply disabling the axis.

Halt should not be required. The Interpreter should quickly detect the Axes have been disabled and Abort.