Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
Posted by
Jon Elson
on 2000-10-13 16:24:07 UTC
Art Fenerty wrote:
to accelerate
smoothly at the beginning and decelerate at the end of the move. That
makes it a
lot more complicated. Also, moving at 8192 steps/sec is unattainable
(with a simple,
as opposed to computerized microstepping drive that smooths out the
rate) because
the next lower speed is 4096 steps/sec. That is a 2:1 jump, and no
stepper
motor could follow it. Even the next lower jump , from 2730 Steps/sec
to 4096
won't work. Regularly scheduled interrupts won't hack it, unless they
are going
at a MUCH faster rate, or you resign yourself to about a thousand
steps/sec
as the maximum rate.
Jon
> Sorry mat, I misunderstood your question. I think that using 8192Yup, the Bresenham line routine looks good, until you realize you need
> interrupts/second and then always interrupting at that frquency, I
> should be
> able to make a table of how often to pulse. This gives me a
> granularity of
> 122 us (roughly) and then by using a common algorithm (similar to that
> used
> for drawing lines in x,y axis) pulse at the algorithm calculated
> times. It
> won't be perfect , but it just might work to make a very smooth linear
> ramp.
> On the
> other hand I could be wasting my time, but thats what programming is
> all
> about.
to accelerate
smoothly at the beginning and decelerate at the end of the move. That
makes it a
lot more complicated. Also, moving at 8192 steps/sec is unattainable
(with a simple,
as opposed to computerized microstepping drive that smooths out the
rate) because
the next lower speed is 4096 steps/sec. That is a 2:1 jump, and no
stepper
motor could follow it. Even the next lower jump , from 2730 Steps/sec
to 4096
won't work. Regularly scheduled interrupts won't hack it, unless they
are going
at a MUCH faster rate, or you resign yourself to about a thousand
steps/sec
as the maximum rate.
Jon
Discussion Thread
Jon Elson
2000-10-12 23:47:34 UTC
Re: step pulse timing resolution
Matt Shaver
2000-10-13 05:19:20 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
Art Fenerty
2000-10-13 12:07:19 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
Jon Elson
2000-10-13 12:21:23 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
Jon Elson
2000-10-13 16:24:07 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
ballendo@y...
2000-10-13 20:27:20 UTC
Re: Re: step pulse timing resolution
ballendo@y...
2000-10-13 20:53:54 UTC
Re: Re: step pulse timing resolution
Jon Elson
2000-10-13 23:34:21 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: step pulse timing resolution
ballendo@y...
2000-10-14 00:13:36 UTC
Re: Re: Re: step pulse timing resolution
Anne Ogborn
2000-10-14 00:41:36 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: step pulse timing resolution
Art Fenerty
2000-10-14 05:12:10 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: step pulse timing resolution
Terry Ackland
2000-10-14 06:11:58 UTC
Re: step pulse timing resolution
Art Fenerty
2000-10-14 10:51:37 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution
ballendo@y...
2000-10-14 11:54:21 UTC
Re: step pulse timing resolution
Alan Marconett KM6VV
2000-10-14 12:22:12 UTC
Re: [CAD_CAM_EDM_DRO] Re: step pulse timing resolution