Re: upgrade problems

["Lawrence Glaister" <lg-at-jfm.bc.ca>]

Hi Ian,
I have freqmod running on a 133 with the PERIOD = 0.000048 (3 times the old
default value). It just barely survives with tkemc as the display... things
are quite usable using
xemc or yemc as the display. The Tkemc overhead makes using the mouse a
pain, but it machines things fine. I just copied librcs.so to my
/usr/local/lib directory. I would recommend going the cvs route instead of
the Aug11 release. In the Aug release, there is a problem with vel/accel
spikes being introduced in the motion profiles when the axis change
direction. This seems to be fixed in the cvs code.
hope this helps get you going
=======================================================
Lawrence Glaister VE7IT             email: lg-at-jfm.bc.ca
1462 Madrona Drive                  http://jfm.bc.ca
Nanoose Bay BC Canada
V9P 9C9
=======================================================
----- Original Message -----
From: Ian Wright <Ian-at-iw63.freeserve.co.uk>
To: Multiple recipients of list <emc-at-nist.gov>
Sent: Wednesday, November 29, 2000 1:54 PM
Subject: upgrade problems


>
> Hi,
>
> I'm trying to experiment with an up-to-date version of EMC on my linux
> 2_0_36 box without screwing up the working version I have on there. I have
> installed the August 200 emcbin version in /usr/local/emc and copied (I
> think) all the missing bits across from my previous installation (which is
> in /usr/local/nist/emc). However, the new version won't run and keeps
giving
> error messages that it can't find librcs.so. I've looked through all the
> files that seem to mention this file but I don't seem to be able to find
> anywhere that points to its location so I'm at a loss as to where I should
> make a link from to /usr/local/rcslib/plat/linux_2_0_36/lib which is where
> librcs.so seems to be.
>
> Can anyone point me in the right direction please?
>
> I also want to try using freqmod rather than steppermod - has anyone set
it
> up on a 100MHz machine - if so could you tell me the changes needed to the
> ini file to save a lot of experimentation time?
>
> Thanks,
> Ian
> --
> Ian W. Wright
> Sheffield  UK
> www.iw63.freeserve.co.uk
> ----- Original Message -----
> From: "Jon Elson" <jmelson-at-artsci.wustl.edu>
> To: "Multiple recipients of list" <emc-at-nist.gov>
> Sent: 29 November 2000 06:27
> Subject: Re: hardware driver
>
>
> >
> >
> > "Terry L. Ridder" wrote:
> >
> > > hello;
> > >
> > > the makefiles and .def files are "interesting".
> >
> > I got a pretty large package from Eric, and it has all the stuff
> > necessary to build the diag program as a separate piece.
> > (Maybe this is all in EMC already, I don't know.)
> >
> > Anyway, the tar.gz file is exactly what Eric sent me, and
> > it has a number of errors, partly due to my poor description
> > of the hardware, partly due to Eric's writing the code at
> > 2 AM, i think.
> >
> > Anyway, there are 3 C files and an include file which are
> > the only things I needed to change to make it work (as far
> > as it does) with my hardware.
> >
> > Thanks,
> >
> > Jon
> >
>
>
>