Re: EMC & Linux

Matt,
Sorry to hear you are still sick. It sure is a drag when you have things you
need to do.

> -----Original Message-----
> From: "Matt Shaver" <mshaver@...>
> > From: Fred Proctor
> > To: mshaver@...
> > Subject: Feed rate override and max feed rate
> > Date: Saturday, June 05, 1999 6:49 PM
> >
> I think the 60, 60, 60, 30 scenario is the correct one. The way this is
> handled in other cncs is that the rapid traverse rate is greater than the
> highest allowable _programmed feed rate_. Also, the feed override control
> usually only goes up to 125%. For example, on a mill that rapids
> at 150ipm,
> the max feed rate you can program might be 100ipm which can be
> increased to
> 125ipm with the feed override knob.
>
> Some random ideas:
>
> 1. Add a MAX_PROGRAMMED_FEED_RATE parameter to allow setting up the
> conditions described above. The writer of the .ini file could
> always goof up
> and allow MAX_PROGRAMMED_FEED_RATE x MAX_FEED_OVERRIDE > MAX_VELOCITY, but
> the maximum actual velocity should never exceed MAX_VELOCITY.
>
> 2. Maybe there should be a "clipping" indicator when this error condition
> happens.
>
> 3. Maybe there should be an _actual_ feed rate display to compliment the
> _commanded_ feed rate display we have now. If we go to the "exact path"
> motion control system this would show when the system is forced
> to decrease
> the feed rate to keep acceleration within bounds.
> If anyone else has suggestions on how to handle this, speak up!

I would agree with the scenario giving 60,60,60,30 and also think you should
never be able to do anything that will cause the machine to try and move
faster than what is set in the MAX_VELOCITY parameter. I also think a window
that showed the actual rate you will get (programmed rate X override, not to
exceed MAX_VELOCITY) would be a handy addition. DeskNC offers this feature
and I found it handy.

> There is a ./update script as well that I believe saves your customized
> settings, but I've never used it. If you try it, let me know,
> maybe I should too!

I tried the ./update script and as best as I could tell it didn't do
anything. It took only a second or two to run and gave a number of directory
not found messages. I don't know if the problem is that I am using the
directory structure as you suggested (/usr/local/nist) and it expected
everything to be at /usr/local/emc or whether it just does not work.

Here is what I tried first:
I put the emc-05-jun-1999.tgz file in the nist directory and did tar -xzvf
on it.
Then while still in the nist directory I did ./install and got the above
results.
I finally just did a ./install without a clean or anything and it looks like
it just overwrote all the existing source and library files and then
compiled everything without deleting any of my files that were in the emc
directory.

Don't know if this is the recommended method, but it seems like it did the
job.

Tim
[Denver, CO]