What's new
What's new

Ran With FNC, G-code Doesn't Match Part

charlie gary

Stainless
Joined
Oct 4, 2009
Location
near Seattle, Washington, USA
Just now saw something odd on our Haas VF-2, circa 2012. We were cutting a simple grid pattern in a fixture plate, and the guy on the machine used FNC to access the program right off the flash drive. For the most part it turned out as planned, but one relief groove came up short and one started at the start point of the line next to it and took off on an angle before getting to the straight line it was supposed to cut. We shut the machine down and rebooted it, but I would love to know if this kind of thing is common when using the FNC function on a Haas. :scratchchin:

Thanks for reading.
 
Just now saw something odd on our Haas VF-2, circa 2012. We were cutting a simple grid pattern in a fixture plate, and the guy on the machine used FNC to access the program right off the flash drive. For the most part it turned out as planned, but one relief groove came up short and one started at the start point of the line next to it and took off on an angle before getting to the straight line it was supposed to cut. We shut the machine down and rebooted it, but I would love to know if this kind of thing is common when using the FNC function on a Haas. :scratchchin:

Thanks for reading.

Were you using a proven program?
Are you 100% certain, without a shadow of a doubt sure your program is correct?
After you rebooted, did the problem repeat the error?
Is the file to big for the machine memory?
If not, how does it run from memory?
If to big, condese the program to the problem area and run from memory. What happens?
 
It wasn't a proven program. I was cutting a grid pattern in a fixture block, so it was only run once. I wondered what had happened with the code, so I imported the g-code back into surfcam and it looked like it was supposed to. At this point I am pretty sure the program is correct, but it's short enough for me to paste it down bellow for all to see.
It was a one-time only program, so I can't say how it would run from memory. I would hope it would run like all the other programs I've run to date.

Here's the code:

%
O0001
(CUT GROOVES IN FIXTURE)
G17 G40 G80 G90
(CUT GROOVES )
T13 M6
M1
S8000 M3
M8
G0 G90 G54 X4.9688 Y0
G43 Z1. H13
G0 Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X0 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X0.375 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X-0.375 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X4.9688 Y0.375
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X4.9688 Y-0.375
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X0.75 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X1.125 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X1.5 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X-0.75 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X1.875 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X2.25 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X2.625 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X3. Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X3.375 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X3.75 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X4.125 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X4.5 Y-2.3438
Z-0.0186
G1 Z-0.1186 F3.
Y-2.25 F10.
Y0.75
Y0.8438
G0 Z1.
X4.9688 Y-0.75
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X4.9688 Y-1.125
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X4.9688 Y-1.5
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X4.9688 Y-1.875
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
X4.9688 Y-2.25
Z-0.0186
G1 Z-0.1186 F3.
X4.875 F10.
X-0.875
X-0.9688
G0 Z1.
M9
G28 G91 Z0
G0 G90 X0 Y0
M30
%

Here's a picture of the machine's interpretation:

prog error.jpg
 
Last edited:
I needed another round on a grooved fixture plate, so I ran the same program again. Same flash drive, same FNC file path, same cutter, same everything except the person pushing the buttons. Part turned out just like it was supposed to.
 
I needed another round on a grooved fixture plate, so I ran the same program again. Same flash drive, same FNC file path, same cutter, same everything except the person pushing the buttons. Part turned out just like it was supposed to.

I didn't really look at your code, but first thing that comes to mind now after seeint the picture is, did the first operator stop and then restart the program?
Go look at the machine if it's not to late and look to see if program restart is ON or OFF.

In my experience, 9 out of 10 times, weird things like this are usually operator error of some sort. Sometimes you can figure out what happened and sometimes not.
 
I suppose I could, but since it ran as advertised the second time around I don't expect it to show any errors. We're too busy making parts right now to go back and check, and I've already re-used that particular flash drive so the program we ran would have to be reposted and reloaded. I think I'll have to chalk this one up to "WTF?"
 








 
Back
Top