There is certain G-Code syntax which works fine in NCPlot but which produces errors when loaded into Mach3.
I do not know which program is "correct"... and I don't really care. What I care about is work flow. Right now I write and debug my G-code programs in NCPlot before transferring them via flash drive to my Mach3 machine (a Tormach which is not networked).
I almost always have to fix something once the program is transferred over. Then I have to transfer the fixes back to my development machine or risk repeating the mistake. Time is money.
Is there a way to have NCPlot flag these syntax errors for me the first time around? NCPlot is a great development tool- worth the price (I wish I could justify the convenience of buying a second license for the Mach 3 computer) and I'm looking forward to the upcoming 3D graphics simulation feature.
Examples of Mach 3 versus NCPlot:
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 left side with brackets "#110=[#110+40.0]"
2. "(xxxx" 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". (OK- I fixed this one by changing the machine configuration)
Thank you!