Re: following error question

["Richard Everett" <rick-at-skyko.com>]

----- Original Message -----
From: "Dam" <damg-at-1st.net>
To: "Multiple recipients of list" <emc-at-nist.gov>
Sent: Thursday, October 03, 2002 6:32 AM
Subject: Re: following error question


>
> Richard Everett wrote:
>
> >Thanks Jon.  I knew velocity 10 would mean 600ipm, I was just trying to
test
> >out the 1.4ghz machine to see if it would bog down.
> >
> >I have not messed with CYCLE_TIME (it is still 0.001 for x,y an z), but I
> >know I have done more than 1000 steps per second.  I measured 5khz step
> >pulses on my oscilloscope.  How exactly does CYCLE_TIME effect max
> >steps/sec, and what do you think is going on in my case?
> >
> >Richard
> >
>
> Richard
>
> I've been developing a servo system using smdromod. It is working pretty
> good on the bench.  I have observed that the period parameter is what
> determines max step pulse rate.  If period is set too small the computer
> just locks up when trying to start EMC.  On a AMD k6 450 MHz I am able
> to run with period set to 0.000016, which is 16 micro seconds.  With a
> scope on the step pin my max pulse rate worked out to be approximately
> 16 us high + 16us low = 32 us/cycle,  32 us/cycle = 31250 Hz.
>
> Axis CYCLE_TIME as I understand it controls the rate at which the
> velocity command or pulse rate is updated. For CYCLE_TIME = 0.001 the
> velocity command or pulse rate is updated once every millisecond.  I
> have not tried setting CYCLE_TIME any lower than 0.001
>
> Dale
>
>
>
>

Ok, now I am getting confused.  What is smdromod?  It sounds like that
actually performs better than steppermod or freqmod.  What are the ups and
downs of using smdromod?

Richard