Messages

1

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

« on: June 01, 2010, 01:17:49 PM »

No, it's not really financial. It's a tech support issue. If you tweak the settings you can screw up the machine making it inaccurate or unreliable. They got tired of diagnosing and fixing problems created by customers tampering with the factory settings. If you want to tamper with your machine they'll tell you how... if you sign a waiver. They still answer support questions after you sign the waiver. I'm happy with the machine and the support.

I wish Apple would do the same thing with the iPhone- you shouldn't have to jailbreak your phone just to use it in a manner they don't sanction.

2

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

« on: February 01, 2010, 07:27:17 PM »

Tormach has disabled many of the menu items including "G-Code Var Monitor". They will "unlock" the missing features If I sign an agreement releasing them from liability and warranty claims.

My machine is already out of warranty and I need to debug my G-Code so I don't really have any choice. One of the reasons I chose the machine (it is an AWESOME machine) was because it came with a Mach3 license. I didn't realize there was "fine print".

3

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

« on: January 30, 2010, 05:48:52 PM »

I do not have that option on my operator menu. The only choices I have are "Control Offline", "Maintenance Hours", and "Set Normal Condition".


 Is this something that Tormach has disabled in their default configuration? Does it require a version newer than 2.42?

Thanks,

-Erik

4

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!

5

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

« on: January 13, 2010, 06:02:45 PM »

NC Plot also claims to follow the "Fanuc standard".

The Mach 3 manual mentioned the NIST NGC (EIA-274-D?) which defines "#".
http://www.isd.mel.nist.gov/personnel/kramer/pubs/RS274NGC_3.web/RS274NGC_33a.html

Mach3 follows this standard more strictly than NC Plot.

Search and replace is certainly one approach. A script using regular expressions could automate things.

The NC Plot folks have indicated their willingness to help.

-Erik

6

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?