Hi friends, now i am using the new version of match the .033 and it is better, is respecting their limit of aceleration of 150mm/seg^2 in all time, also now work a 25khz of kernel speed and no have problem with the movement of mouse and change of window, neither use it much.

But no understand, maybe it happen a your, when press FeedHold my mill stop in two seconds when would should stop in less of 0.5 seconds. The indicator numeric also delay 2 seconds to stop. I see wich the match react later de 1.5 seconds to stop and the rest the use to desaceleration the motor. It is normal?.

When i used is a 60khz, the mill stopped more rapid.

regards.
Renato

Have you tried using this version at 60khz? if yes does it reduce the delay in feedhold?
Hood

Hi hood, no still probe 60khz in version .033 tomorrow make this. From a beginning i have worked at 25khz.
In the version 3.037 60khz stop more rapid the motors compared with 25khz. but a 60khz can happen aceleration high o delta of position.

regards

Try the latest rev, there have been some issues with the last few revisions and some computers.
Hood

I proved the last version .035 and have the same result a 25khz of kernel speed the Feedhold stop the axis more slow compared with 60khz.
I prefer use FeedHold instead of stop, the stop is very abrupt.

My PC is Dell P4, 512Mbram.

Is it normal?, I will lack some configuration?.  this is a bug?

regards

I am afraid I use the SmoothStepper on all my machines so I am unable to test to see what time the feedhold takes, maybe somone else will let you know.
 You should only use Stop in an emergency or when all motion has already halted or you are likely to lose position so youu are doing things correctly by using the Feedhold.
Hood

Try changing the setting in genreal config, "No FRO on queue". However, it may introduce a delay in the FRO.