518 posts · page 14 of 44.
Standard G-code states fixed coordinates; parametric programming computes them from variables. One is a recipe with exact amounts, the other a recipe with formulas.
PlanetCNC and Mach3 both speak the PC-controller family's standard-shaped subset: the core ports cleanly, and the edges, M-codes, cycles, deserve the check.
On a Pocket NC, five-axis G-code means A and B words joining the familiar three, CAM doing the orientation math, and you reading the result. The orientation.
On a PrintNC you are operator and machine builder at once, so G-code trouble has three suspect layers: the program, the post, and the configuration you wrote.
RepRap and Marlin G-code shares a skeleton with LinuxCNC but not a vocabulary. The code-by-code translation map, plus the G28 trap that crashes machines.
A retrofitted Bridgeport speaks whatever dialect its new controller brought: the basics are the standard core, knee-mill Z realities, and config awareness.
The safe pre-door sequence is three commitments in code: retract Z by a route you calculated, stop the spindle, and stop the program. The two retract idioms.
Sandvik Coromant's training is metal-cutting theory at vendor depth. The free alternative is a stack: their own knowledge pages, a simulator, and drills.
Sinumerik 828D and Fanuc share the motion core and split at the cycle layer: CYCLE calls vs canned cycles, R-parameters vs macros, and one unit landmine.
G97 locks the lathe spindle to one RPM, so you compute it yourself: surface speed and diameter in, RPM out. The formula, the diameter choice, the cases.
The SYIL X7 has shipped with different controls across years and markets, so its G-code list is a per-unit question: identify the control, then the list.
A turning insert cuts with a radius, not a point, and tapers and arcs show the difference. How TNR comp works, the orientation number, and the lead-in rules.