Re: EMC steps/rev calibration-SOLVED

Hi Ray,

I'll follow the steps you've outlined, and let you know the results.

I am shutting down EMC via the menu, for a clean departure. As you
know, I am new to Linux and, as such, have a limited ability to
diagnose the problem. My description of persistent processes comes
from the FAQ description of similar behavior, previously noted.

It's curious that this issue has not been addressed in EMC, since the
problem has been around for awhile. I've seen a few posts here
describing similar behavior. Clearly it's a problem that doesn't
affect every installation, perhaps setup or hardware specific.

This may not be the best place for continued discussion of this
topic. I've been reading the EMC mailing list site, however have not
figured out how to post there, though I have signed up. I'll begin a
discussion there once I am able.

Thanks for your input.

r

--- In CAD_CAM_EDM_DRO@y..., Ray Henry <rehenry@u...> wrote:
>
> R
>
> Would you describe which persistent processes you know are left in
there and
> what the evidence of them hanging around is?
>
> Are you shutting down the emc by using one of the buttons or menus
in the gui
> itself rather than killing a terminal that you started it in! When
you shut
> down the EMC the proper way, the terminal script keeps working and
tries to
> remove a bunch of semaphores, modules, and such. I am in sympathy
here
> because I have seen stuff left around here when I am developing and
make a
> mess of things.
>
> If this is a BDI 2+ and if your problem is mbuff, reboot fixes it.
Or you
> might go into /usr/src/rtlinux/drivers/mbuff, start a terminal and
issue the
> command make. After a bit it will tell you to issue the command
make test.
> This done there will be several new executables in that directory.
Now you
> can issue the command
>
> ./mbuff_dealloc emcmotStruct
>
> If you get the answer open failed then it is not mbuff that is
hanging
> around. If it says "emcmotStruct shared memory area was 667* bytes
long"
> then you know you have accomplished something. Repeat the command
until it
> reports that the area was 0 bytes long and then issue the command
>
> /sbin/rmmod mbuff
>
> /sbin/lsmod will list the modules that have been left around.
>
> > I've put a lot of work into getting EMC running.  I hope doesn't
turn
> > out to be so flakey it's not useable.
>
> Me too! <g> There seem to be a lot of others making parts with it.
>
> Ray
>
>
> On Tuesday 04 June 2002 02:58, you wrote:
> > Message: 12
> >    Date: Tue, 04 Jun 2002 00:23:06 -0000
> >    From: "nahydro" <r_fl_z@h...>
> > Subject: Re: EMC steps/rev calibration-SOLVED
> >
> > My pleasure:
> >
> > http://www.linuxcnc.org/handbook/faq/faq/x524.html
> >
> > also useful
> >
> > http://www.linuxcnc.org/handbook/faq/faq/book1.html
> >
> > While I have now properly set my INPUT_SCALE value, I am still
> > fighting this slow down by persistent processes. I've seen several
> > posts from others with the same behavior.
> >
> > I've put a lot of work into getting EMC running.  I hope doesn't
turn
> > out to be so flakey it's not useable.
> >
> > r