We were impressed at how many readers can write g-code programs from scratch. In fact the overwhelming majority read, write, or tweak programs on a regular basis. If you're not yet able to do that, you should learn. If you're at the "Read or Tweak" stage, you should advance to being able to write programs from scratch. Armed with a good understanding of g-code, you can:
- Avoid having to run back to your CAM program when simple changes to the g-code would do the job.
- Learn how to improve the g-code the CAM program puts out for better results.
- Understand better how to tweak your CAM software's post processor so it produces better code from the start.
- Get a second opinion on the CAM's g-code before you find out something's wrong at the machine.
- Make it faster and easier to fix the g-code when you run into a problem due to a bug in the CAM or post processor.
- Create quick and dirty g-code programs that allow you to get on with machining faster without having to sit down with your CAD/CAM.
- Develop a greater facility for working at the console of the machine directly.
These are all valuable skills that increase your productivity as a CNC machinist. According to the survey, many of you have already figured that out!
G-Code from the Machine's Perspective
There are a handful of basic concepts you should know before we dive into what individual g-codes do and how to use them. Most importantly, you must understand what a computer language is and how to think about it. G-Code is a computer language aimed at telling your machine what to do. The trouble with computer languages like g-code is that unlike people, machines are very literal. They assume you know exactly what you want, they don't question you about it, and they immediately try to comply, even if that means hurting themselves!
For that reason, you need to adopt an approach of being protective of your machine, perhaps even over protective bordering on paranoid. It will do exactly what you tell it to even if that means rapiding a spinning cutter with 20HP behind it directly into your expensive fourth axis and destroying it. There's no need to be afraid of g-code, but it is important to understand it and to respect it in order to be successful. Getting to that stage is another excellent reason to spend time learning the g-code. It will give you insights into your machine that enable you to extract more performance and to protect it better from accidents.
G-Wizard G-Code Editor
Speaking of understanding g-code and protecting the machine, throughout this course we will be setting up to do exercises using the G-Wizard G-Code Editor. Think of it as a convenient etch-a-sketch on which you enter g-codes and can immediately see the toolpath that results. This makes learning a lot faster and easier when you have that immediate response versus trying to plot things on graph paper or work with your machine controller. In addition, you can make your mistakes on a simulator rather than with the actual machine until you get a lot more comfortable in your ability to command the machine successfully.
GWE has a "Hints" window that shows you what each code does in plain English...
With GWE, you can study the g-code from the comfort of your armchair and let it sink in. More importantly, GWE gives you lots of additional information that's hard to get at with most controllers, and it has a host of features to help you through the process of learning g-code. For example, it's "Hints" feature tells you what each code does in plain English.
We'll be including some exercises with each section that involve working with GWE. From time to time we'll also include videos that help illustrate how to go about using GWE for the exercises.
1. If you don't already have GWE, take a moment now to sign up. We'll be using it for many of the exercises on each section of this course.
2. Watch the G-Wizard Editor Getting Started Tour video, it's a quick and easy intro:
The G-Wizard Editor Getting Started Tour...
3. If you'd like to learn more, we have provided an optional chapter about G-Code Editors.