gustafson
Diamond
- Joined
- Sep 4, 2002
- Location
- People's Republic
So
2021 Speedio s700X2
The program originated in fusion CAD/CAM
proven program, stored in machine
hundreds of parts run, in several runs over several months
One day it up and cleans off a .406 drill
Now since the part is held down by a couple 1/4 SHC I have had to mod some moves on occasion and later modded it to run multiple locations
SO I fix the program and off I go.
Happens again on another program
Ok, I go through all the programs I can see for similar parts[I run dozens of similar parts] and fix them by inserting a G00 Z.9 or something.
fast forward to today
First I run a part that I still have labelled as test so not truly proven although I have probably made good parts with it
the second half of a hole pattern are not all the way through. Ok, maybe it isn't quite right, only need a couple, figure it out later
I go to run the program that initially had a problem a few weeks ago.
Now it drills this second half of the hole pattern not all the way through
This it the subroutine for the hole drilling. There is a tool call and G52[offset from previously defined g54] and call this subroutine. 3 times 3 parts. First 5 holes drill fine, second 5, shallow
There is a SHC screw between the holes at lines 1105 and 1108, thus the G00 Z.899 move, have to kill the G81 and redefine it
So, WTF!
NOw if you tell me the code is wrong, ok, fine, I fix it
But then, why the FOOOK did it run for months before?
Look, I am new to G Code, I have used Heidenhain for 30 years, and if you write a program in heidenhain, it runs, it will run, for 30 years.
2021 Speedio s700X2
The program originated in fusion CAD/CAM
proven program, stored in machine
hundreds of parts run, in several runs over several months
One day it up and cleans off a .406 drill
Now since the part is held down by a couple 1/4 SHC I have had to mod some moves on occasion and later modded it to run multiple locations
SO I fix the program and off I go.
Happens again on another program
Ok, I go through all the programs I can see for similar parts[I run dozens of similar parts] and fix them by inserting a G00 Z.9 or something.
fast forward to today
First I run a part that I still have labelled as test so not truly proven although I have probably made good parts with it
the second half of a hole pattern are not all the way through. Ok, maybe it isn't quite right, only need a couple, figure it out later
I go to run the program that initially had a problem a few weeks ago.
Now it drills this second half of the hole pattern not all the way through
This it the subroutine for the hole drilling. There is a tool call and G52[offset from previously defined g54] and call this subroutine. 3 times 3 parts. First 5 holes drill fine, second 5, shallow
There is a SHC screw between the holes at lines 1105 and 1108, thus the G00 Z.899 move, have to kill the G81 and redefine it
So, WTF!
NOw if you tell me the code is wrong, ok, fine, I fix it
But then, why the FOOOK did it run for months before?
Look, I am new to G Code, I have used Heidenhain for 30 years, and if you write a program in heidenhain, it runs, it will run, for 30 years.