When creating G code for production runs or product runs … programmers are usually looking for the fastest and easiest code. As long as it gets the job done … machining is good … machining time is good … that will do. But there is a very IMPORTANT aspect of G code that is rarely taken into consideration … let’s dive in.

Let’s start with the understanding that the machine being programmed will NOT last forever. Upgrading equipment or replacing older equipment will eventually mean that that G code being created will need to be run on another machine. Maybe a newer machine with a newer CNC control … maybe just another machine that is replacing the current machine … maybe just another machine in the shop as the desired machine is busy and not able to run the parts when needed. That means the G code needs to FLEXIBLE.

What does that mean exactly?

Being the creators of our KIPWARE G code conversion applications … we see it all the time … G code needs to be converted from one format to another to be run on a different machine than the one the G code was originally prepared. If the original program was created with simple, straight forward G code … not usually an issue.But if the programmer used macro or variable type programming … or if the program was created in a non-G-code format like Mazatrol or Hurco … that code cannot be converted to standard G code and therfore the programmer is stuck running that code on only a compatible machine / control.

This is an important FACT to consider when creating CNC programs.

“Conversational” controls like Mazatrol or Hurco are easy to program … but when considering the future … those programs cannot be moved to machines / control requiring “standard’ G code. Users are locked into that CNC control to run those programs.

The industry standard is what is referred to as “fanuc compatible” G code. Fanuc, Haas, even Okuma run a “standard” type of G code that can easily be converted between formats with tools like KIPWARE. This gives the users flexibility in the future when new equipment is being considered … or even in the day to day shop where moving G code between machines is essential. “Fancy” macro or variable programming looks great … the programmers looks super intelligent … but the reality is those programs are flexible when considering the “REAL WORLD”.

Just something to THINK about.

So … to be a good CNC programmer … you need to also think about the future. Is the G code I’m creating today going to be able to be converted … upgraded … to meet the future possibilities? Future equipment requirements?

Kenney Skonieczny – President
Kentech Inc.