Yes I agree now. Its what the CAM program generated. I'm dissecting it
and playing around with it. I dont get the G0 with no parms. I'm not
a GCODE expert,but I will be soon:-), I was hoping the CAM output was
ready to go as is. This is a good example to learn the details and
wonder why did it generate that...
-Lee
--- In mach1mach2cnc@..., "David Gabrielsen"
<cimdave@f...> wrote:
You got a whole Russian novel on one line.
Break it up into smaller logical chunks.
Especially the dwell
dg
Message: 21
Date: Sat, 23 Aug 2003 23:11:08 -0000
From: "Lee Studley" <indigo_red@q...>
Subject: N106G0G90G54X0.Y2.7969A0.S5000M93G4P2
Hi Art,
I finally got around to loading up Mach2 and I've been having
problems. Mach1 runs fine( with its caveats)
This code is from a standard FANUC postprocessor. This is a portion
of a file that runs fine in Mach1. In Mach2 it chokes with opening
the file during the"regen.. path"
message dialog on this line: N106G0G90G54X0.Y2.7969A0.S5000M93G4P2
Also once limits have been tripped, I used to be able to reset and
move the machine off the limit switch. I cant find how to do that
now
in Mach2. Is there an override. I just read thers and overide
button,
now I 'm looking for it :0)
Also, I've tried both drivers and the machine has dumped Mach2 out
twice. Going back to the original driver. I get the WinXP message
"blahblah MAch2 has done something evil and do you want to send a
report to MS blah blah."
-Lee
