Topics

1

G-Code, CAD, and CAM discussions / G-Code debugging printf? how can I see my parameters?

« on: January 29, 2010, 05:10:22 PM »

I want debugging printf() or something like it for G-Code.

I have a G-code program which is not doing what I expect it to. I would like to examine some parameters/variables after the program runs in order to see what's happening.
I don't care how: output to a text file, a MSG to the screen, whatever. I just want to see the value of "#130" after the program stops.

I tried using "MSG," but could not get it to evaluate expression- it just dumps the literal string "#130"

I am using the Tormach flavor of Mach3 (2.42)

Thanks!

2

G-Code, CAD, and CAM discussions / syntax differences between Mach3, NCPlot, and others

« on: January 13, 2010, 03:59:24 PM »

(I posted a similar question on the NC Plot forum.)

There are syntax differences between different flavors of G-code. Programs which plot correctly in NC Plot generate errors in Mach 3. Is the G-code standard poorly defined? Are there bugs in one or the other? Is there anything I can do in Mach 3 to make it accept programs which it currently chokes on? Some compilers have different error and warning levels. Could I tell Mach 3 to ignore certain errors (like incomplete comments)?

Here are examples which work in NC Plot but not in Mach 3:

1. "#110=#110+40.0"
This line is OK in NCPlot but generates an error in Mach3. In Mach 3 I have to enclose the right side with brackets "#110=[#110+40.0]"

2. "(*********x" NCPlot allows comment lines with only an opening parenthesis. Mach3 gives an error unless there is a matching closing parenthesis.

3. "[-#110]" works fine in NC plot but not in Mach3. In Mach 3 I use "[0-#110]".

4. NCPlot by default treats "10" as ".010". Mach3 treats it as "10.0". I was able to fix this one in NC Plot by changing the machine configuration.

Any ideas?