Using the Setting_StepperEnableDelay or $680 setting

[MadTooler]

I made a simplified assumption that the Setting_StepperEnableDelay that is also set by the $680 = 250 would simply halt any further instructions until the delay had been passed after enabling of the stepper motor drive pin. It may be that my setting of $1=255 delay before disabling the stepper drive pin may be a conflicting issue. What I find is surging motion as it appears to enable then disable then enable then disable etc. with both of those settings.

What I am trying to do: I turn off my motors with the M18 via the stepper enable control plugin. When I turn them back on with M17, I need a slight delay for the steppers to clock and settle so I can get a good read of their integrated encoders before I start processing any of the gcode with good closed loop accuracy. I have a built in delay in my motor driver of 200 milliseconds. I was hoping the $680 would allow me to set it at 250 ms to avoid trying to send step/dir ticks until the driver has done its thing. Will it work for this task?

[terjeio]

The plugin has a potential issue since the M-codes are executed immediately even if there is buffered motion, I'll change that to delay them until all buffered motion is completed.
The $680 delay is only applied when transitioning from IDLE state to a motion state so the potential issue might be the cause.

Setting $1=255 will disable automatic stepper disable on motion completed, thus it cannot interfere with anything.

[MadTooler]

Do you see the order of timing as I did?

[terjeio]

I have been busy and away for a while, heading out now for a party. Will be back at grblHAL stuff tomorrow (I am at UTC+7).

[MadTooler]

All good. Have fun.

[terjeio]

New attempt committed and Web Builder updated - hopefully ok now.

[MadTooler]

Excellent! That did it!