Re: [CAD_CAM_EDM_DRO] emc final questions

whollid1@... wrote:

> Now that I have emc up and running I only have 2 glitches left
>
> 1: when i try to load in a g-code file I usually fill the first few
> lines with the modal codes I.E. g17,g21,g40,etc. However if I try to
> load g53 or g10 the program will not run it and instead loads the
> default g54 (When I delete g53/g10) which calls out to my var file,
> and if I change the var file to 0,0,0 it interprets that as machine
> 0,0,0 not my part 0,0,0

Don't expect EMC to take the exact same dialect of G-code that
some other machine uses. It is its own flavor.

I use G92 to set the part coordinate system. If you haven't done
a G92 on all the axes, then it will have to use the machine coordinate
system. Certain commands "reset" EMC, and cause you to lose the
part coordinate system.

>
> 2: with the bdi install on my 200 pentium, about every other time i
> try to do the first jog after starting the system/program I get a
> lockup so severe I have to do a power off reboot. Nothing
> works...mouse keys.. nothing. Anyone else had this!

Yes, this is a known problem. There are some definitions for the
stack size of the real time component of EMC that were made too small.
You will have to recompile the whole works. There should be instructions
on how to do that. But, I think you will have to upgrade the BDI install to

the "developer" level of install, instead of the user level. You should be
able to just re-run the CD install, but select update and developer, and
it should add the extra components. In the /usr/local/emc/src/emcmot
directory, there are 3 files, emcmot.c, emcsegmot.c and emcstepmot.c,
which define the stack size in the c code. Look for the text RT_STACK_SIZE
and SM_STACK_SIZE, and change the value to 4096 if it was only
2048. Then run the compile script from /usr/local like this ./compile
There should be lots of lines of text scrolling by for a while, and you
should get new versions of the executable code. That should fix
that particular problem.

Jon