Re: freqmod.o in EMC started, now questions
Posted by
Jon Elson
on 2000-01-29 23:10:40 UTC
Tim Goldstein wrote:
output velocity request. FF1 is applied before the trajectory velocity
goes into the above calculation, and it adds a term for rate of change
of the required velocity. It helps sluggish drives by effectively increasing
gain when the trajectory has a change in velocity.
If so, you need to reduce P. This is actually a crude method, and not
really desirable. A better way is to hack the code to allow a deadband.
You figure out what this range of hunting is, in terms of linear units,
and if the absolute value of the position error is less than this figure, you
set error equal to zero. Assuming this is a small range of a few ten-thousandths,
it should have almost no effect on accuracy or smoothness.
Jon
> From: "Tim Goldstein" <timg@...>P is the proportional gain. So, error is multiplied by P to give the
>
> OK, with the EMC Board of Knowledge online I have gotten EMC to come up with
> the new freqmod.o module for steppers and it does run the machine with
> faster movements.
>
> Now for the questions:
> What does the P and the FF1 parameter you play with really do?
output velocity request. FF1 is applied before the trajectory velocity
goes into the above calculation, and it adds a term for rate of change
of the required velocity. It helps sluggish drives by effectively increasing
gain when the trajectory has a change in velocity.
> Why do my steppers sit and buzz after a move? I actually think I know thisI gather you are using encoders with stepper motors?
> answer which I think is the steppers are hunting back and fourth about
> .0002" trying to get where the feedback position matches the expected
> position, but the steps are not fine enough to get a zero difference. I do
> see the actual positions oscillating a few ten thousands. So, the real
> question is not why, but how do I get them to just sit still when at rest?
If so, you need to reduce P. This is actually a crude method, and not
really desirable. A better way is to hack the code to allow a deadband.
You figure out what this range of hunting is, in terms of linear units,
and if the absolute value of the position error is less than this figure, you
set error equal to zero. Assuming this is a small range of a few ten-thousandths,
it should have almost no effect on accuracy or smoothness.
Jon
Discussion Thread
Tim Goldstein
2000-01-29 15:01:04 UTC
freqmod.o in EMC started, now questions
Matt Shaver
2000-01-29 17:23:27 UTC
Re: freqmod.o in EMC started, now questions
Jon Elson
2000-01-29 23:10:40 UTC
Re: freqmod.o in EMC started, now questions
Tim Goldstein
2000-01-29 23:49:56 UTC
RE: freqmod.o in EMC started, now questions
Jon Elson
2000-01-30 20:09:59 UTC
Re: freqmod.o in EMC started, now questions