Re: EMC error reporting, radius compensation

Art

Each time that you run verify it finds only the next error. There have
been some problems with reporting errors since the introuduction of the
newer six axis interpreter. It works better if you run from a terminal
rather than an icon because you can see the error messages -- or at least
the look ahead messages and they will report the line number if you have
full debug set in your ini file.

BTW -- i wouldn't try using a full circle. Use half circles for a bit
here. These problems should be fixed by the next BDI release at names.


HTH

Ray

On Wednesday 20 March 2002 11:19 pm, you wrote:
> Message: 19
>    Date: Thu, 21 Mar 2002 03:05:50 -0000
>    From: "snuckleton" <snuckleton@...>
> Subject: EMC error reporting, radius compensation
>
> I am using the EMC system and I'm trying to debug
> a GCode program.  When I open, and then verify my
> program, EMC may report errors but it doesn't give line
> numbers or any context for the error.  Is there any way to get more
> details on the errors?
>
> Also, I'm finding that after modifying my program, saving the file,
> doing an Open in EMC, then verify - the first error it reports seems
> to be a leftover from the previous version of the program file. Clicking
> Verify again gives me fresh errors.
>
> Finally, does anyone have a simple program that uses G41 or G42
> to do cutter radius compensation?  This is what I'm trying to
> figure out.
>
> Thanks
> Art