Repost: Re: Lost Steps => time for microprocessors!

Below is what I remember from my E-groups trashed? post this morning.
It's a response to msg #10495

>I don't want it to keep jogging for up to .2 seconds AFTER I take my
>finger OFF the jog buttons! So I always up the GUI rate to 10 Hz.
>If the GUI were going much more than 10 hz, the numbers would be a
>blur.

>Jon

Jon,

If EMC keeps going (putting out steps)in jog mode after you stop
pressing the key, it surely should be regarded (and reported)as a
bug!

Jog should be: press jog key,steps output,GUI updated at some
arbitrary rate. Release jog key, steps stop immediately, current
position is updated with next GUI update.

Of course, if the control is set to one inch (or other increment) jog
per press, the above does not apply.

But the update rate of the coords display should never determine the
step output,IMO. Thats the cart driving the horse!

Flashcut updates the display each 1/4 or 1/2 second and it works fine.

What we really need is two routines, one for slow jog (update screen
every pulse(or selected number of pulses)); and another for fast jog
which updates only often enough to get us in the ballpark, then we
switch to slow jog. This would also stop the blur problem mentioned
above.

Ballendo